You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
external-dns usually called external DNS outside from the cluster, which may caused NXDOMAIN "error" in CoreDNS. This feature allowed users to customize the workload DNS resolution.
What is the feature you are proposing to solve the problem?
There was no way to set dnsConfig or dnsPolicy for kubernetes workload, thus making it impossible to set custom nameserver and custom nameserver config for the pod.
Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.
Name and Version
bitnami/external-dns 6.36.1
What is the problem this feature will solve?
external-dns usually called external DNS outside from the cluster, which may caused NXDOMAIN "error" in CoreDNS. This feature allowed users to customize the workload DNS resolution.
What is the feature you are proposing to solve the problem?
There was no way to set dnsConfig or dnsPolicy for kubernetes workload, thus making it impossible to set custom nameserver and custom nameserver config for the pod.
Similar feature to this PRs Kafka DNSPolicy and DNSConfig or kubernetes-sigs/external-dns PR.
I'm planning to contribute.
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: