ovn-kubernetes
ovn-kubernetes copied to clipboard
Add support for DNSNameResolver
This PR adds the support for DNSNameResolver in ovnk as per the enhancement proposal openshift/enhancements#1335.
This feature is enabled via a new flag enable-dns-name-resolver. However, enable-egress-firewall flag should also be set for this feature to be enabled.
cluster-manager watches for events related to EgressFirewall objects and creates/deletes the DNSNameResolver objects based on the events.
ovnkube-controller watches DNSNameResolver to get the latest IP addresses associated with a DNS name. resolver is initialized instead ofegressFirewallDNS and it is used to create/destroy/update address sets related to DNS names.
If the enable-dns-name-resolver is not enabled, then the behavior of ovnk doesn't change.
coverage: 52.689% (+0.3%) from 52.418% when pulling 6788da1e5f5c664fc59da1156103acb0b2ab2379 on arkadeepsen:dnsnameresolver into 9bf6a484cb7a4ea486114061cd06880ff06f4432 on ovn-org:master.
@npinaeva I have made the suggested changes. PTAL.
Deploy Preview for subtle-torrone-bb0c84 ready!
| Name | Link |
|---|---|
| Latest commit | c9a21692ed203436694402547b65a1d20d59fc5f |
| Latest deploy log | https://app.netlify.com/sites/subtle-torrone-bb0c84/deploys/662936d36165a50009a01690 |
| Deploy Preview | https://deploy-preview-4045--subtle-torrone-bb0c84.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
btw https://github.com/ovn-org/ovn-kubernetes/pull/4251 got merged
btw #4251 got merged
@npinaeva updated code accordingly
thank you for patience and a great contribution @arkadeepsen!
Thanks @npinaeva for providing your feedback and suggestions to the PR.
Can we add e2es to make sure this new feature works?
that is planned as a separate PR, as it requires some more work to add dnsresolver to the kind cluster here https://github.com/openshift/coredns-ocp-dnsnameresolver. The feature will need only the operator provided by ^ to work. In openshift it is deployed as a part of cluster-dns-operator, but we need some more time to make it work with kind.