aws / aws/containers-roadmap

[EKS] [Feature request]: Configuring Nodes to Authenticate to a Private Repository

Open
#1,882 1 comment 2 reactions 0 assignees View on GitHub
EKS Proposed
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

Contributor guide

Open the contributing guide

Research direction

Start with the request and the Kubernetes documentation on imagePullSecret, then compare its pod- and namespace-level scope with the requested node- or cluster-level authentication. The payload names no repository files, tests, or entry points; done would require a defined EKS approach for authenticating node image pulls from private registries.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, docker, kubernetes
Domain
authentication, cloud, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.