Cause: Hard-coded Cluster DNS (172.30.0.10) in kubelet configuration template.
Consequence: Windows Containers on Windows Nodes get assigned a wrong DNS Server IP, hence DNS resolution does not work.
Fix: Remove the hard-coded Cluster DNS information and parametrize the value as a command-line argument.
Result: Windows Containers on Windows Nodes get assigned a valid DNS Server IP and DNS resolution works for Windows workloads.
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 (Red Hat OpenShift support for Windows Containers 3.1.2 product release), 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/RHBA-2022:7076
oc get network cluster -o yaml apiVersion: config.openshift.io/v1 kind: Network metadata: creationTimestamp: "2022-03-06T07:36:50Z" generation: 2 name: cluster resourceVersion: "3575" uid: e2b65b50-c594-46b4-9bd6-1f55aa244999 spec: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 externalIP: policy: {} networkType: OVNKubernetes serviceNetwork: - 172.30.0.0/16 status: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 clusterNetworkMTU: 8901 networkType: OVNKubernetes serviceNetwork: "clusterDNS":["172.30.0.10"]