search

kubernetes-sigs / external-dns

Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
Apache License 2.0
7.64k stars 2.55k forks source link

Make DNSEndpoint CRD GA #2941

Open snorwin opened 2 years ago

snorwin commented 2 years ago

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.

snorwin commented 2 years ago

https://github.com/kubernetes-sigs/external-dns/issues/2529 https://github.com/kubernetes-sigs/external-dns/issues/2936

snorwin commented 2 years ago

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, ...).

k8s-triage-robot commented 1 year ago

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

snorwin commented 1 year ago

/remove-lifecycle stale

k8s-triage-robot commented 1 year ago

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

k8s-triage-robot commented 1 year ago

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

illrill commented 1 year ago

/remove-lifecycle rotten

k8s-triage-robot commented 1 year ago

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

k8s-triage-robot commented 1 year ago

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

onedr0p commented 1 year ago

/remove-lifecycle rotten

jstudler commented 6 months ago

@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.

snorwin commented 6 months ago

@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 map[string]string in the status could simplify certain provider implementations.

k8s-triage-robot commented 3 months ago

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

snorwin commented 3 months ago

/remove-lifecycle stale

k8s-triage-robot commented 4 days ago

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