Loading...

XML

Word

Printable

Type: Bug
Resolution: Can't Do
Priority: Major
Fix Version/s: None
Affects Version/s: 4.9.z
Component/s: Windows Containers
Labels:
None

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
3
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:
None
Release Blocker:
Rejected
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Priority Data:
PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

Windows container/pod does not resolve onpremise DNS as the linux pods

Version-Release number of selected component (if applicable):

OCP 4.9 annd Windows Operartor 4.0.1

How reproducible:

Deploys OCP 4.9 with windows operator (set to manual upgrade).

Steps to Reproduce:

1. deploys windows container
2. try nslookup from windows pod
3. try nslookup from linux pod

Actual results:

the windows podd returns the kubernetes ip instead of coreDNS(external configured) as expected.

Expected results:

the windows pod should return/resolve the same as the linux pod which is the external dns.

Additional info:

Assignee:: Team WinC

Reporter:: Renato Puccini

Need Info From:: None

Contributors:: None

QA Contact:: None

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2022/10/11 7:07 PM

Updated:: 2025/09/13 3:26 PM

Resolved:: 2022/12/07 7:51 PM