-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KCP: support pluggable in-cluster DNS providers #3698
Comments
similar comment as in:
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/lifecycle frozen |
Close in favor of #5491 |
@vincepri: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
User Story
As a user, I would like to create a new cluster using an in-cluster DNS provider of my choosing, instead of having kubeadm install CoreDNS, because I'd like to use something other than CoreDNS from the start.
As a user, I would like to manage my in-cluster DNS provider separately from KCP, decoupling their lifecycles, so that I'm in control of my DNS provider.
(Maybe out of scope?)
As a user, I would like to influence the initial CoreDNS configuration when bootstrapping my control plane, because my cluster needs custom CoreDNS settings to function correctly (both at bootstrapping time and beyond).
(Maybe out of scope?)
As a user, I would like an easy way to manage my CoreDNS configuration, including preserving my customizations when CoreDNS is upgraded.
Detailed Description
See user stories
Anything else you would like to add:
Something like a CoreDNS Operator might be useful or necessary for some of these stories.
kubeadm is currently responsible for installing CoreDNS and we'll need to be able to disable that.
/kind feature
/milestone Next
The text was updated successfully, but these errors were encountered: