Update existing clusters for auto-scaling
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
I have verified my auto-scaling configurations by creating a new EKS anywhere cluster on vSphere with auto-scaling using the cluster auto-scaler deployment. It works perfectly in tandem with HPA.
However, when I try to edit the cluster configuration of an existing EKS anywhere cluster on vSphere with auto-scaling configurations (minCount/maxCount) in the exact same manner as above and apply updates through upgrade command., the upgrade goes through without reporting any errors. However, when I observe the cluster configuration, auto-scaling configurations are absent.
Is this a bug or this is how it's supposed to happen. In other words, can we apply auto-scaling configurations to an existing cluster which was not created with auto-scaling parameters
thanks,
Ambar
Contributor guide
Research direction
Begin with the cluster configuration and upgrade command paths for an existing vSphere cluster, then compare them with creation using minCount/maxCount and the cluster auto-scaler deployment. Reproduce the update and verify whether the existing cluster retains the auto-scaling configuration; document whether applying it after creation is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100