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
After updating the kubernetes_version to KubernetesVersion.V1_24 (was KubernetesVersion.V1_23) only EKS and the first NodeGroup ("main_group": "true") got updated to the 1.24.
The other group was kept at 1.23.
I didn't specify any release_version on NodeGroup creation because on the docs it is said that the default behavior is to follow the current Kubernetes version.
Cluster version:
Different version from NodeGroup to the other (I edited the names in html to make it more clear to read):
MainNodeGroup Kubernetes version:
SecondaryNodeGRoup Kubernetes version:
Also I tried to add some tags to see if cdk is updating something at all and it is, but the kubernetes version of the second group is kept at 1.23.
I tried to lower and raise the autoscaling group capacity to trigger some EC2 instance creations with no result.
Is this a bug?
If not how can i trigger the update of the second group using cdk?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to update a cluster with 2 different nodegroups in a testing environment from 1.23 to 1.24.
The first group is made up of only on-demand instances, the other one only of spot ones.
This is snippet of the code used to create 2 NodeGroups in Python:
After updating the
kubernetes_version
toKubernetesVersion.V1_24
(wasKubernetesVersion.V1_23
) only EKS and the first NodeGroup ("main_group": "true"
) got updated to the 1.24.The other group was kept at 1.23.
I didn't specify any
release_version
on NodeGroup creation because on the docs it is said that the default behavior is to follow the current Kubernetes version.Cluster version:
Different version from NodeGroup to the other (I edited the names in html to make it more clear to read):
MainNodeGroup Kubernetes version:
SecondaryNodeGRoup Kubernetes version:
Also I tried to add some tags to see if cdk is updating something at all and it is, but the kubernetes version of the second group is kept at 1.23.
I tried to lower and raise the autoscaling group capacity to trigger some EC2 instance creations with no result.
Is this a bug?
If not how can i trigger the update of the second group using cdk?
Am I doing something wrong in the code?
Beta Was this translation helpful? Give feedback.
All reactions