Allow a host name pattern to be specified for DNS management
What
With DNSPolicy you target a gateway and all listener hosts have their dns managed by default. There maybe some hostnames that you do not want to have managed by the on cluster DNS controller. This maybe because the DNS configuration required is not supported or because you already have the dns configuration you need or is in a different provider.
Options
While we want to able to target specific listeners with DNS Policies #515. This will help but does not solve the entire problem set and potential creates a poor experience.
If I have 3 listeners A,B and C and I want A and B to have their dns managed in the same way but I don't want C to have its dns managed at all, I cannot do this currently. When we allow targeting listeners, I can but it will mean duplicating the policy for listener A and B. This is cumbersome and if you add more listeners even more so.
Suggestion:
Allow a pattern to be defined in the DNSPolicy that is used to decide whether a given host should have its dns managed. Report in the status block when a hosts dns is managed or not. Flag if no hosts are managed by this policy
@maleck13 Review section name - can it be a regex or some other flexibility in targeting.
most likely to be resolved via changes in gateway api