[EKS] [request]: Overview of Kubernetes Services Installed with Addon
- 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**
Please provide a method similar to "helm get all chartname" for AWS EKS addon's(describe-addon-all/describe-addon-info) to list Kubernetes services installed as part of the chart/addon, facilitating clearer understanding and management.
**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?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now?
To get the list of installed kubernetes resources and default values/ extra added values as part of the plugin. i dont find this solution as part of describe-addon,describe-addon-configuration,describe-addon-versions
What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
manually figure out the each services installed as part of the
**Are you currently working around this issue?**
Manually Validating kubernetes service using the labels but this will not display all the resources(Ex: Clusterrole,Rolebinding etc..,)
ex: kubectl -n kube-system get all --selector=eks.amazonaws.com/component=coredns
**Additional context**
Anything else we should know?
None
**Attachments**
None
Contributor guide
Research direction
Start by reviewing the EKS addon APIs named in the request: describe-addon, describe-addon-configuration, and describe-addon-versions, then compare them with the kubectl label-based workaround. The issue’s desired outcome is a method that lists every Kubernetes resource installed by an addon, including ClusterRole and RoleBinding objects, along with default and extra values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100