[EKS] [request]: Expose add-on installer logs
- 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**
What do you want us to build?
When installing EKS add-ons, there is no visibility into the installer. It's incredibly frustrating if something isn't working. The add-on install times out after >1hour and even then, the error may be ambiguous or misleading. See CaseID: 14108622841 for a good example of how frustrating that is. It appears that AWS Support also cannot see installer logs, so it ends up being a lot of guesswork.
**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? 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.
**Are you currently working around this issue?**
How are you currently solving this problem?
Guesswork
**Additional context**
Anything else we should know?
**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Contributor guide
Research direction
The issue identifies EKS add-on installation as the affected service but names no repository files, tests, or implementation entry points. Start by determining whether this public roadmap request has an AWS-side implementation path; done would require installer logs to be exposed and the timeout and ambiguous-error problem to be verifiably addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100