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

Activating DNSAnnotation controller #48

Closed
FullyScaled opened this issue May 6, 2021 · 0 comments · Fixed by #55
Closed

Activating DNSAnnotation controller #48

FullyScaled opened this issue May 6, 2021 · 0 comments · Fixed by #55
Labels
area/networking Networking related kind/enhancement Enhancement, improvement, extension priority/3 Priority (lower number equals higher priority)

Comments

@FullyScaled
Copy link

How to categorize this issue?

/area networking
/kind enhancement
/priority 3

What would you like to be added:

Activation of DNSAnnotation Resource (https://github.com/gardener/external-dns-management/blob/master/examples/70-dnsannotation.yaml)

Why is this needed:

The dns.gardener.cloud/dnsnames annotation currently cannot be used together with the istio ingressgateway that comes when using kyma. Those annotations will be lost during upgrades. Therefore its required to create an independent resource for letting gardener set dns entries. DNSEntry does not support referring kubernetes services directly. Since IP-Adresses of cloud provider loadbalancers can change, there is the need for the DNSAnnotation in a kyma based usage scenario.

@FullyScaled FullyScaled added the kind/enhancement Enhancement, improvement, extension label May 6, 2021
@gardener-robot gardener-robot added area/networking Networking related priority/3 Priority (lower number equals higher priority) labels May 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking Networking related kind/enhancement Enhancement, improvement, extension priority/3 Priority (lower number equals higher priority)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants