-
Notifications
You must be signed in to change notification settings - Fork 752
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
while applying new deployment, microk8s showing container creating for an extended period #4293
Comments
Can you share an inspection tarball from the cluster where you are having an issue? Can you create a pod that gets stuck in "Creating" status, then share the output of Thanks! |
Hi @neoaggelos here is the output of the command
|
From the events of the pod, it looks like Calico has not yet started and configured itself on the node. What's the status of Thanks! |
Hi @neoaggelos both if we have not deleted both calico's, the container I am trying to create will not get created forever. |
Unfortunately I cannot help further without some more logs from the services themselves. Can you share an inspection report? There should be something related in the logs of containerd, at the very least. Thanks! |
Hi @neoaggelos, Please provide the full details of the logs you require and steps or commands to get those. thanks! |
Please share an inspection tarball, which you can create by running |
Hi @neoaggelos , please find the attachment. |
I seem to be getting into this state reliably after a few hours of fresh cluster creation, not really sure where to look │ Warning FailedCreatePodSandBox 83s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "62356903f11f2c438f14ad416a89 │ |
In my case seem related to the service account token |
This appears to have been caused by remnants of the older version of calico that ships with microk8s (described in /var/snap/microk8s/current/args/cni-network/cni.yaml) after attempting to upgrade, it seems to work for a while until new calico presumably tries refreshing its token. Ensuring that this was properly removed fixed my issues |
Hi @tszyszko , I installed microk8s with homebrew on my mac. I usually keep it up-to-date. still having the same problem. could you please elaborate the steps you have followed. thanks! |
@tszyszko +1 |
Summary
running microk8s long time makes this issue, while applying new deployment, microk8s showing container creating for an extended period. it will not create the container. also, if we try to delete, status will change to pending(for deletion)
What Should Happen Instead?
microk8s is supposed to create the container
Reproduction Steps
Introspection Report
Can you suggest a fix?
it was a problem calico controller and calico node. when I descibe the pod, it shows me this. I tried deleting calico controller and calico node, once k8s starts new calico node and calico controller, the deployment container I applied will be created and running.
Are you interested in contributing with a fix?
no
The text was updated successfully, but these errors were encountered: