EKS Auto Mode [request]: documentation update for add-ons
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
Is there an EKS Auto Mode-specific page that describes:
- which add-ons are provided as "default"
- which are "self-managed"
- some third option?
I found mention of Auto Mode [here](https://docs.aws.amazon.com/eks/latest/userguide/workloads-add-ons-available-eks.html) but nothing to say what's default on which platform.
The column, `Compatible compute types` confirms compatibility; I would't infer from compatibility that it's cluster default.
The [Considerations for Amazon EKS Auto Mode](https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html#addon-consider-auto) confirms what is default on the cluster with odd phrasing
> With Auto mode compute, _many commonly used EKS add-ons become redundant_, such as:...
Specifically, one page suggests that the [vpc-cni](https://docs.aws.amazon.com/eks/latest/userguide/workloads-add-ons-available-eks.html#add-ons-vpc-cni) plugin is "redundant", while the other says that is compatible with EC2. That's a bit confusing.
---
Recommendation: one, simple table with a few columns:
| Add-on | EKS | Auto Mode
| ---------- | ------------ | ----------- |
| add-on-1 | your problem | default
| add-on-2 | your problem | your problem
etc
Contributor guide
Research direction
Start with the linked EKS add-ons available page and the Considerations for Amazon EKS Auto Mode section, comparing their treatment of vpc-cni and other add-ons. Done means documenting a clear table that distinguishes default, self-managed, and other relevant states for EKS and Auto Mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100