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
Currently when a customer upgrades the kubernetes version for their cluster, we don't check if the packages bundle has the same kubernetes version as the cluster. We should add a validation to block the customer from upgrading their cluster if the kubernetes version in their cluster spec doesn't match the kubernetes version in the active bundle of their package bundle controller. This will force customers to upgrade their active package bundle to the latest version corresponding to their kubernetes version specified in the cluster spec. The Upgrade cluster section in the EKS-A docs also needs to be updated to let customers know that they need to upgrade their active package bundle too every time they upgrade their cluster to a newer kubernetes version.
Currently when a customer upgrades the kubernetes version for their cluster, we don't check if the packages bundle has the same kubernetes version as the cluster. We should add a validation to block the customer from upgrading their cluster if the kubernetes version in their cluster spec doesn't match the kubernetes version in the active bundle of their package bundle controller. This will force customers to upgrade their active package bundle to the latest version corresponding to their kubernetes version specified in the cluster spec. The Upgrade cluster section in the EKS-A docs also needs to be updated to let customers know that they need to upgrade their active package bundle too every time they upgrade their cluster to a newer kubernetes version.
This should also fix #8984
The text was updated successfully, but these errors were encountered: