You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. What kops version are you running? The command kops 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
a kops 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?
The text was updated successfully, but these errors were encountered:
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?
/kind bug
1. What
kops
version are you running? The commandkops version
, will displaythis information.
Client version: 1.27.3
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.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?
The text was updated successfully, but these errors were encountered: