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.

Sign up for GitHub

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

Jump to bottom

CoreDNS for cluster DNS #3951

Closed
johnbelamaric opened this issue Nov 28, 2017 · 7 comments
Closed

CoreDNS for cluster DNS #3951

johnbelamaric opened this issue Nov 28, 2017 · 7 comments
Assignees
@rajansandeep
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
1.10

Comments

@johnbelamaric
Copy link
Member

  1. Describe IN DETAIL the feature/behavior/change you would like to see.

Implement the K8s 1.9 alpha feature: kubernetes/enhancements#427

  1. Feel free to provide a design supporting your feature request.
@johnbelamaric
Copy link
Member Author

cc @rajansandeep @fturib

@johnbelamaric
Copy link
Member Author

See also: kubernetes/community#1100

@justinsb justinsb added this to the 1.9 milestone Nov 28, 2017
@chrislovecnm
Copy link
Contributor

I have to mean to drop this in. This is actually a great starter issue, which would help a person learn kops.

  1. add manifest to upup addons - it is just like the PRs for CNI providers
  2. add API changes for user to select dns
  3. test test test

@johnbelamaric
Copy link
Member Author

Great! @rajansandeep is going to take a look.

@rajansandeep rajansandeep mentioned this issue Dec 11, 2017
Merged
@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 Feb 27, 2018
@chrislovecnm
Copy link
Contributor

/lifecycle frozen
/remove-lifecycle stale

@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 Feb 27, 2018
@justinsb justinsb modified the milestones: 1.9.0, 1.10 May 26, 2018
@rajansandeep
Copy link
Contributor

/close

@rifelpet rifelpet added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. and removed good-starter-issue labels Apr 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rajansandeep rajansandeep

Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
1.10
Development

No branches or pull requests
7 participants
@justinsb @chrislovecnm @rifelpet @johnbelamaric @k8s-ci-robot @rajansandeep @fejta-bot