Add preflight check on custom CNI during upgrade
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
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`.
Contributor guide
Research direction
Start with the EKS-A upgrade CLI and its existing preflight validations. Reproduce or inspect the upgrade path for a cluster with a custom CNI and check how cniConfig.cilium.skipUpgrade is read. Done means the upgrade fails before attempting to install built-in Cilium when a custom CNI is present and that setting is not true.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100