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
If a user runs EKS-A upgrade CLI on a cluster with custom CNI installed (not default EKS-A Cilium) without specifying cniConfig.cilium.skipUpgrade: true, the upgrade will stall at "Cilium unable to be installed" because EKS-A tried to install its built-in Cilium on a cluster that already had custom CNI.
We should add a preflight validation in upgrade to fail ahead when a custom CNI presents on the cluster and cniConfig.cilium.skipUpgrade is not set to true.
The text was updated successfully, but these errors were encountered:
If a user runs EKS-A upgrade CLI on a cluster with custom CNI installed (not default EKS-A Cilium) without specifying
cniConfig.cilium.skipUpgrade: true, the upgrade will stall at "Cilium unable to be installed" because EKS-A tried to install its built-in Cilium on a cluster that already had custom CNI.We should add a preflight validation in upgrade to fail ahead when a custom CNI presents on the cluster and
cniConfig.cilium.skipUpgradeis not set totrue.The text was updated successfully, but these errors were encountered: