-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Open
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.
Description
I'd like to use a CRD as a source, but the --crd-source-kind flag doesn't seem to do anything.
For example, I modified crd-manifest.yaml to change the name of the sample custom resource from "DNSEndpoint" to "XDNSEndpoint" and created a resource using that CRD. Then I ran:
$ build/external-dns --kubeconfig="$KUBECONFIG" --provider inmemory --source crd --crd-source-kind="XDNSEndpoint"
What happened:
INFO[0000] Using kubeConfig
INFO[0000] Created Kubernetes client https://192.168.254.10:16443
DEBU[0000] groupVersion externaldns.k8s.io/v1alpha1
ERRO[0005] no kind "XDNSEndpointList" is registered for version "externaldns.k8s.io/v1alpha1" in scheme "pkg/runtime/scheme.go:100"
What you expected to happen:
external-dns lists XDNSEndpoint resources and uses them as DNSEndpoint sources.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Slack discussion thread: https://kubernetes.slack.com/archives/C771MKDKQ/p1631820191048300
Environment:
- External-DNS version (use
external-dns --version): external-dns-helm-chart-1.2.0-33-g8cc95229-dirty - DNS provider:
- Others:
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.