-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
system-cluster-critical pod "calico-kube-controllers" is not yet ready over 10 minutes when performing rolling update #10207
Comments
for me it sometimes can take longer than 10 minutes, that is why I use 20minutes max time for waiting |
@zetaab Good to know that we're not alone. 😆 |
@CheyiLin This is a Calico and client-go issue, unrelated to kOps. Please more about it in: |
@hakman The issue projectcalico/calico#3751 is exactly what I reported here. |
No problem. Keep an eye on those. I see there's some activity. |
@hakman |
1. What
kops
version are you running?Version 1.18.2 (git-84495481e4)
2. What Kubernetes version are you running?
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
kops rolling-update cluster --name my-cluster-name --yes
5. What happened after the commands executed?
The cluster cannot pass the validation, wait for the rescheduled system-cluster-critical pod
calico-kube-controllers
to be ready.kops logs
pod calico-kube-controllers logs
6. What did you expect to happen?
The rescheduled pod
calico-kube-controllers
will be ready in few minutes.7. Please provide your cluster manifest.
kops cluster & ig manifests
8. Please run the commands with most verbose logging by adding the
-v 10
flag.Paste the logs into this report, or in a gist and provide the gist link here.
Not available yet.
9. Anything else do we need to know?
calico-kube-controllers
manually solves the issue, the new created pod works normally, and the cluster can pass the validation, continue the rolling update process.new created pod calico-kube-controllers logs
The text was updated successfully, but these errors were encountered: