[EKS] [CoreDNS]: Ability to select/provide CoreDNS image used in managed CoreDNS EKS Addon #2538
Labels
EKS Add-Ons
EKS Networking
EKS Networking related issues
EKS
Amazon Elastic Kubernetes Service
Proposed
Community submitted issue
Tell us about your request
A capability to either select from a series of supported CoreDNS images or provide a reference to an arbitrary CoreDNS image in the EKS-managed CoreDNS addon.
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?
We're currently investigating different options for cross-cluster service discovery using the MCS API.
According to your own AWS Cloud Map MCS controller intro post, a new CoreDNS image is required to use the
multicluster
CoreDNS plugin.I've validated this is still the case with the current provided version of EKS-managed CoreDNS.
This exact case could be solved by adding the
multicluster
plugin to the EKS CoreDNS standard image, but I think a more generic solution would be helpful to the community.Are you currently working around this issue?
Run a separate unmanaged CoreDNS instance with the required addons and use a forward rule for the
clusterset.local
domain using a custom Corefile.This is fine for development/low volume but introduces additional complexity and point of failure.
The text was updated successfully, but these errors were encountered: