[eks] [request]: Better documentation for kube-proxy version
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
Better documentation for which version(s) of `kube-proxy` are supported.
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
The `kube-proxy` version in the [EKS Upgrade Guide](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html) doesn't line up with the K8s version used in the [AMI releases](https://github.com/awslabs/amazon-eks-ami/releases) (and has regressed for v1.18, v1.17 & v1.16) or the versions available in the ECR public container registry.
**Are you currently working around this issue?**
n/a
**Additional context**
n/a
**Attachments**
n/a
Contributor guide
Research direction
Compare the kube-proxy versions in the EKS Upgrade Guide with the Kubernetes versions in the amazon-eks-ami releases and the versions available in the ECR public container registry. Done means the supported kube-proxy versions are documented consistently, including the noted v1.16, v1.17, and v1.18 regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100