-
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
Switching an existing ASG-based instance group to use instanceRequirements
rather than instances
fails
#15304
Comments
Can confirm, have same issue |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
We seem to have a similar issue. So just to check, what did you have as In our case we created the group initially with There is a check for the spot instances here: kops/upup/pkg/fi/cloudup/awstasks/autoscalinggroup.go Lines 536 to 539 in db26ad5
However, there is no such check for the Same seems to be the case here: kops/upup/pkg/fi/cloudup/awstasks/autoscalinggroup.go Lines 431 to 435 in db26ad5
And here: kops/upup/pkg/fi/cloudup/awstasks/autoscalinggroup.go Lines 743 to 752 in db26ad5
|
/remove-lifecycle rotten |
/kind bug
1. What
kops
version are you running? The commandkops version
, will displaythis information.
1.26.2
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.1.26.3
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
Deploy a cluster with an instance group that specifies some instance types under
spec.mixedInstancesPolicy.instances
. Then update the instance group manifest and replace that section with aninstanceRequirements
section, e.g.:5. What happened after the commands executed?
When running
kops update cluster
with the updated instance group manifest, it gets stuck in a failure loop:FWIW, it doesn't matter whether
onDemandAllocationStrategy: lowest-price
is included in the manifest - the error is the same.6. What did you expect to happen?
The existing ASG should have been updated with the instance requirements specified.
7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml
to display your cluster manifest.You may want to remove your cluster name and other sensitive information.
See snippet above.
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.
See above.
9. Anything else do we need to know?
Creating a new instance group with
instanceRequirements
specified works fine. Switching an existing instance group toinstanceRequirements
also works fine if you delete the existing ASG before runningkops update cluster
.The text was updated successfully, but these errors were encountered: