-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Instance groups stuck in "NeedsUpdate" #7142
Comments
This happened to me after changing to a launch template of mixed instance types and using spot instances. I don't know if related, but otherwise my cluster had no issues up to that point. Running
Despite updating with |
May be related to #7066 with the issue I'm seeing above. |
We appear to be seeing this with kops 1.13.0, k8s 1.13.10, and a kops template with maxPrice We are using |
We are also getting stuck with eternal "NeedsUpdate". In our case I think it is because the following code looks for default version in the launch template: But the default version is the first version, not the latest: I guess default version should be updated when a new template is rolled out? We are generating terraform code which I think might be the issue here. |
Looks like it is a problem related to terraform in our case: |
I am also facing the same issue |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Facing the same issue again. |
I also still experience this error with kops 1.16.0 |
It would be great with a feature in Kops that would show you why an InstanceGroup would need to be updated. A diff of some kind? |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/close |
@hakman: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hello, I encounter this issue with kops 1.18.2 (git-84495481e4). Kubernetes version: 1.14.2 using kops with "+Spotinst" feature flag. |
Submitted new issue #10166 |
1. What
kops
version are you running? The commandkops version
, will displaythis information.
1.12.1
2. What Kubernetes version are you running?
kubectl version
will print theversion if a cluster is running or provide the Kubernetes version specified as
a
kops
flag.v1.12.7
3. What cloud provider are you using?
aws
4. What commands did you run? What is the simplest way to reproduce this issue?
After running
kops rolling-update
, my instance groups are still reporting "NeedsUpdate". I don't understand this, since nodes are literally 5 minutes old. How can I see "why" kops things they need update? I've tried looking at the documentation forrolling-update
parameters but the documentation isn't really clear about what flags are available or what they do.So I guess my bug is: I don't understand why kops reports
NeedsUpdate
for my nodes, and I don't understand how I can figure out why.5. What happened after the commands executed?
Instance Groups are still reporting
NeedsUpdate
.6. What did you expect to happen?
Instance Groups should report
Ready
since they just got rolling-updated.The text was updated successfully, but these errors were encountered: