Skip to content
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

Closed
ncdc opened this issue Sep 25, 2020 · 5 comments
Closed

KCP: support pluggable in-cluster DNS providers #3698

ncdc opened this issue Sep 25, 2020 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@ncdc
Copy link
Contributor

ncdc commented Sep 25, 2020

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

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 25, 2020
@k8s-ci-robot k8s-ci-robot added this to the Next milestone Sep 25, 2020
@neolit123
Copy link
Member

similar comment as in:
#3700 (comment)

the current way is by passing --skip-phase=addons or a specific addons/x.
but i guess for CAPI this has to be supported via the config:
kubernetes/kubeadm#2261

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 25, 2020
@fabriziopandini
Copy link
Member

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 30, 2020
@vincepri
Copy link
Member

Close in favor of #5491
/close

@k8s-ci-robot
Copy link
Contributor

@vincepri: Closing this issue.

In response to this:

Close in favor of #5491
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

6 participants