Open leochr opened 9 months ago
One use case is forcing pod to go through public DNS resolvers. Deny all egress to cluster IP CIDR range using NetworkPolicy. In this case DNS resolution within the pod fails with timed out error. Solution: add public DNS resolvers instead of internal one.
dnsPolicy: "None"
dnsConfig:
nameservers:
- 8.8.8.8
- 1.1.1.1
I think dnsPolicy: "None
is needed otherwise configs are merged for this use case
Confirmed with Artur that the config options in our CRDs that we plan to add .spec.dns.policy
and .spec.dns.config
would be sufficient for the use case described above. So we are good.
Ready for review RCO: https://github.com/application-stacks/runtime-component-operator/pull/615 Tests: https://github.ibm.com/websphere/operators/pull/159 (RCO #969)
Support DNS-related configurations including
dnsPolicy
anddnsConfig
https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/