-
Story
-
Resolution: Done
-
Major
-
None
-
None
Description
This story deals with making use of the WICD controller command when WMCO configures Windows instances. This allows for multiple follow-up stories, moving individual service configuration out of WMCO, and into WICD.
Engineering details
When configuring instances WMCO should annotate the Node object with the desiredVersion annotation, informing WICD of which ConfigMap to use to configure the instance.
If this annotation is later changed to an incorrect value, WMCO's node controller will revert it. WMCO starts WICD as a service.
Acceptance Criteria
- WMCO runs WICD as a Windows service on Windows instances.
- WMCO sets `windowsmachineconfig.openshift.io/desired-version` on nodes, its value must match the WMCO version.
- blocks
-
WINC-737 Move hybrid-overlay configuration to WICD
- Closed
-
WINC-738 Kubelet service is described in services ConfigMap
- Closed
-
WINC-739 Configure azure node manager through WICD
- Closed
- is blocked by
-
WINC-717 WICD controller framework
- Closed
-
WINC-825 WICD reacts to Node and ConfigMap cluster events
- Closed
- links to