-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
Proactive Architecture
-
5
-
False
-
None
-
False
-
WINC - Sprint 248
Description
WICD faces the issue of the kubelet on platform=none Nodes picking an arbitrary IP address, which may not map to the IP used in windows-instances ConfigMap,causing issues mapping the node to the ConfigMap listing.
The solution in https://github.com/openshift/windows-machine-config-operator/pull/1260 is a stopgap and involves passing the node-ip argument
value into the kubelet service command. WICD deduces this value from
the list of BYOH instances described in the Windows instances
ConfigMap. This does not work with WICD's design as stated in the enhancement proposal.
Engineering Details
See https://github.com/kubernetes/kubernetes/issues/104269
Acceptance Criteria
- WICD no longer pulls the windows-instances configmap
- links to
-
RHBA-2023:125706 Red Hat OpenShift for Windows Containers 10.16.0 product release
- mentioned on