We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If you have multiple external DNS instances, for example this one and cloudflare and you add annotations for both on the same ingress, such as:
--- apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: nginx-demo namespace: test annotations: external-dns.alpha.kubernetes.io/hostname: nginx.example.com external-dns.alpha.kubernetes.io/cloudflare-proxied: "false" spec: ingressClassName: nginx rules: - host: nginx.example.com http: paths: - backend: service: name: nginx port: number: 80 path: / pathType: Prefix
Then the mikrotik webhook will complain that cloudflare-proxied is an invalid provider-specific configuration.
cloudflare-proxied
This is likely a bug in the upstream external-dns since we should only be getting our webhook annotations and no vendor-specific ones.
The text was updated successfully, but these errors were encountered:
Relevant: kubernetes-sigs/external-dns#4951
Sorry, something went wrong.
mircea-pavel-anton
No branches or pull requests
If you have multiple external DNS instances, for example this one and cloudflare and you add annotations for both on the same ingress, such as:
Then the mikrotik webhook will complain that
cloudflare-proxied
is an invalid provider-specific configuration.This is likely a bug in the upstream external-dns since we should only be getting our webhook annotations and no vendor-specific ones.
The text was updated successfully, but these errors were encountered: