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

Allow configuring of coredns options #1064

Closed
dionysius opened this issue Aug 16, 2018 · 4 comments
Closed

Allow configuring of coredns options #1064

dionysius opened this issue Aug 16, 2018 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@dionysius
Copy link

Is this a BUG REPORT or FEATURE REQUEST?

FEATURE REQUEST

Kubeadm currently only allows definition of mainly crutial options, while coredns has a good list of options to consider allowing to be set. It is difficult to kubectl patch the wished changes to the configmap in afterwards, so requesting the implementation of these/some options. Personally, I'd like to define ttl, resyncperiod, endpoint_pod_names, transfer and ignore empty_service

Versions

kubeadm version (use kubeadm version): current master branch (see link above)

Environment:

  • Kubernetes version (use kubectl version): unrelated
  • Cloud provider or hardware configuration: unrelated
  • OS (e.g. from /etc/os-release): unrelated
  • Kernel (e.g. uname -a): unrelated
  • Others:

What happened?

I have no options to configure the coredns.

What you expected to happen?

I have at least some options to configure the coredns.

How to reproduce it (as minimally and precisely as possible)?

Can't reproduce, options are missing

Anything else we need to know?

Don't think so

@dionysius
Copy link
Author

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 16, 2018
@neolit123 neolit123 added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Aug 16, 2018
@neolit123
Copy link
Member

neolit123 commented Aug 16, 2018

this is a know problem.
users want to set addon specifics, we but don't support it yet.

it could happen after 1.12.

@neolit123 neolit123 added this to the GA milestone Aug 16, 2018
@neolit123
Copy link
Member

/close

in favor of:
#1091

@k8s-ci-robot
Copy link
Contributor

@neolit123: Closing this issue.

In response to this:

/close

in favor of:
#1091

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. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

3 participants