Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1570399

Summary: [3.8] DNS to local node vs. static egress IP
Product: OpenShift Container Platform Reporter: Dan Winship <danw>
Component: NetworkingAssignee: Dan Winship <danw>
Status: CLOSED CURRENTRELEASE QA Contact: Meng Bo <bmeng>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.8.0CC: aos-bugs, bbennett
Target Milestone: ---   
Target Release: 3.8.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: When using per-namespace static egress IPs, all external traffic is routed through the egress IP. "External" means all traffic which isn't directed to another pod, and so includes traffic from the pod to the pod's node. Consequence: When pods are told to use the node's IP address for DNS, and the pod is using a static egress IP, then DNS traffic will be routed to the egress node first, and then back to the original node, which might be configured to not accept DNS requests from other hosts, causing the pod to be unable to resolve DNS. Fix: pod-to-node DNS requests now bypass the egress IP and go directly to the node Result: DNS works
Story Points: ---
Clone Of: 1570398 Environment:
Last Closed: 2018-08-23 14:15:51 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:
Bug Depends On: 1557924    
Bug Blocks:    

Comment 1 Dan Winship 2018-04-22 15:03:03 UTC
https://github.com/openshift/ose/pull/1219

Comment 2 Dan Winship 2018-08-23 14:15:51 UTC
closing old fixed 3.8 bugs