Bug 1880902
Summary: | need dnsPlocy set in crd ingresscontrollers | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | zhangguanzhang <zhangguanzhang> |
Component: | Networking | Assignee: | Miheer Salunke <misalunk> |
Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | unspecified | CC: | amcdermo, aos-bugs, misalunk |
Version: | 4.5 | ||
Target Milestone: | --- | ||
Target Release: | 4.7.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-24 15:18:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
zhangguanzhang
2020-09-21 04:41:16 UTC
Which platform is this? What DNS policy do you see set? Looking at my AWS cluster I see: $ oc get pods -n openshift-ingress router-default-58db4cf8d4-cv9lc -o yaml |ag dns "dns": {} "dns": {} f:dnsPolicy: {} dnsPolicy: ClusterFirst Target set to next release version while investigation is either ongoing or pending. Will be considered for earlier release versions when diagnosed and resolved. I want to set it to `ClusterFirstWithHostNet` Tagging with UpcomingSprint while investigation is either ongoing or pending. Will be considered for earlier release versions when diagnosed and resolved. (In reply to zhangguanzhang from comment #3) > I want to set it to `ClusterFirstWithHostNet` If the endpoint publishing strategy type is set to host network then we should automatically set the dnsPolicy with ClusterFirstWithHostNet. Would that be your expectation? yes, could add a field let user to set it Verified with 4.7.0-0.nightly-2020-12-04-013308 in vSphere which using HostNetwork and passed. [root@preserve-hongli-ipv6 ~]# oc -n openshift-ingress get deployment router-default -oyaml <---snip---> dnsPolicy: ClusterFirstWithHostNet hostNetwork: true # oc -n openshift-ingress exec router-default-589b49584-fhptg -- cat /etc/resolv.conf search openshift-ingress.svc.cluster.local svc.cluster.local cluster.local hongli-vs47.xxx.com nameserver 172.30.0.10 options ndots:5 # oc -n openshift-ingress exec router-default-589b49584-fhptg -- nslookup kubernetes.default.svc.cluster.local Server: 172.30.0.10 Address: 172.30.0.10#53 Name: kubernetes.default.svc.cluster.local Address: 172.30.0.1 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633 |