-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Make DNSEndpoint CRD GA #2941
Comments
The status of the DNSEndpoint should be improved by at least adding the error message and maybe some provider related status information (e.g. reference for InfoBlox, ...). |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
@snorwin fully agree that we should improve the DNSEndpoint status reporting. What status fields/logs/events/conditions did you have in mind? From my understanding we should at least see in the status of the DNSEndpoint CR whether the RR was synced to the provider or not. |
@jstudler as you mentioned, most important is to know if the DNSEndpoint was synced to the provider and the error message in case an error occurred. The information whether a DNSEndpoint is skipped or does not match the regex filters of the DNS zone or is currently not tracked by the operator (e.g. missing owner TXT record) could also be of interest. I could also imagine that provider-specific metadata (e.g., for tracking references and ID) as a |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The DNSEndpoint specified in a custom resource is very powerful and allows ExternalDNS to be used in many different ways (e.g. custom CNAME for OpenShift routes, managing A records of nodes in a Open Cluster Management context, setting a TXT records for a ACME DNS challenge). It would be really awesome to have this feature GA.
This issue is meant to track the missing features for the CRD to become GA.
The text was updated successfully, but these errors were encountered: