aws / aws/containers-roadmap

[EKS] [request]: Support pulling coredns from private image repository

Open
#1,394 0 comments 5 reactions 0 assignees View on GitHub
EKS EKS Add-Ons
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 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
Support pulling coredns from private image repository instead of AWS managed ECR which is the current EKS behaviour.

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?
Our customer security policy requires all container images running on EKS should be coming from the enterprise private repository (JFrog Artifactory). However when bootstrapping an EKS cluster, currently EKS is pulling coredns image from an AWS managed ECR, i.e. 602401143452.dkr.ecr.ap-southeast-2.amazonaws.com/eks/coredns:v1.8.0-eksbuild.1. So would appreciate if we have an option to allow EKS to pull coredns image from enterprise private repo instead so we can be aligned with customer's security policy.

Are you currently working around this issue?
We currently are asking a temporary exemption. However it needs to be addressed as a formal solution.

Additional context

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

Open the contributing guide

Research direction

The issue identifies EKS cluster bootstrapping and the CoreDNS image URI as the relevant entry points, but names no repository files or tests. Start by locating the EKS/CoreDNS image configuration and determine how private repository settings would be represented. Done means EKS can pull CoreDNS from an enterprise private repository instead of the AWS-managed ECR image.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.