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

DNS service is installed for shoots without DNS domain #4

Closed
rfranzke opened this issue Feb 20, 2020 · 0 comments · Fixed by #5
Closed

DNS service is installed for shoots without DNS domain #4

rfranzke opened this issue Feb 20, 2020 · 0 comments · Fixed by #5
Assignees
Labels

Comments

@rfranzke
Copy link
Member

What happened:
Shoots that don't specify a DNS domain (.spec.dns = nil) or that are scheduled to a seed that is tainted with "DNS disabled" still get the DNS service.

What you expected to happen:
The DNS service shoot only be installed for shoots with a DNS domain.

How to reproduce it (as minimally and precisely as possible):
Create a shoot with .spec.dns=nil and register the DNS extension (globally enabled). See it getting the DNS service pod.

  • Gardener version (if relevant): v1.0.4
  • Extension version: v1.3.0
  • Kubernetes version (use kubectl version): doesn't matter
  • Cloud provider or hardware configuration: doesn't matter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants