I encountered the same issue in my tests, and what I observed is that all the pods are healthy and properly created on the MicroK8s side.
Upon further investigation, it appears that when using a VM that meets the basic requirements outlined in the documentation[0] and employs an HDD disk, timeouts tend to occur frequently. On the other hand, when conducting the same test with an SSD disk to host the VM and increasing the CPU resources, timeouts no longer occur.
During the testing with the HDD, I noticed a high iowait, ranging from 30~50, and a significant number of CPU spikes. Ideally, we should explore options to extend the timeout for the bootstrap process.
I encountered the same issue in my tests, and what I observed is that all the pods are healthy and properly created on the MicroK8s side.
Upon further investigation, it appears that when using a VM that meets the basic requirements outlined in the documentation[0] and employs an HDD disk, timeouts tend to occur frequently. On the other hand, when conducting the same test with an SSD disk to host the VM and increasing the CPU resources, timeouts no longer occur.
During the testing with the HDD, I noticed a high iowait, ranging from 30~50, and a significant number of CPU spikes. Ideally, we should explore options to extend the timeout for the bootstrap process.
[0] https:/ /microstack. run/docs/ single- node-guided