Description of problem: When a cluster is created with a different cidr and service network, The ClusterDNS IP in kubelet.conf should change accordingly. However on a windows node, it is still 172.30.0.10. How reproducible: Always Steps to Reproduce: Check the kubelet.conf on any windows node. Actual results: The clusterDNS is 172.30.0.10 even when the serviceNetwork is 100.123.0.0./16. Expected results: The cluster DNS should be a IP in 100.123.0.0/16 which is the serviceNetwork for the cluster.
*** Bug 1992228 has been marked as a duplicate of this bug. ***
oc get network cluster -oyaml apiVersion: config.openshift.io/v1 kind: Network metadata: creationTimestamp: "2021-11-30T11:43:26Z" generation: 2 name: cluster resourceVersion: "3110" uid: 9198cca0-4dcc-468c-b9fb-15f9e7465f91 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: - 172.30.0.0/16 "clusterDNS":["172.30.0.10"] verified on version "5.0.0+69a4fee"
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: Windows Container Support for Red Hat OpenShift 5.0.0 [security 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-2022:0577