Open gerasym opened 3 months ago
Hi @gerasym. If you run kops update cluster
do you see that it tries to change onDemandAllocationStrategy to lowest-price
?
If you change it via AWS console, is it possible?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/kind bug
1. What
kops
version are you running? The commandkops version
, will display this information.Client version: 1.27.3
2. What Kubernetes version are you running?
kubectl version
will print the version if a cluster is running or provide the Kubernetes version specified as akops
flag.v1.26.13
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
kops update cluster --yes
5. What happened after the commands executed?
The cluster was created with mixed instance group, but On-Demand allocation strategy is set to Prioritized
6. What did you expect to happen? On-Demand allocation should be set to lowest-price according to instance group configuration
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.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.9. Anything else do we need to know?