-
Story
-
Resolution: Done
-
Major
-
None
-
None
Description
This story moves the configuration of the hybrid-overlay service out of WMCO's responsibility and into WICD. WMCO will now set the service ConfigMap's data to include information on how to configure hybrid-overlay, instructing WICD to do it. Because service configuration will be temporarily split between WMCO and WICD, WMCO must wait until the hybrid-overlay service is fully configured, and then continue the current configuration process.
Engineering Details
WMCO's actions should look like this:
1) ConfigMap is properly set up
2) Run WMCB init-kubelet
3) Set desired version annotation on node
4) Wait for hybrid-overlay to be fully configured
5) Continue configuration
Acceptance Criteria
- WMCO does not directly start hybrid-overlay service anymore
- Service ConfigMap contains hybrid-overlay service info
- blocks
-
WINC-733 Instance cleanup is done by WICD cleanup command
- Closed
-
WINC-740 Configure kube-proxy through WICD
- Closed
-
WINC-741 WICD takes more responsibility of Node configuration
- Closed
- is blocked by
-
WINC-731 Run WICD service on Windows instances
- Closed
-
WINC-848 Windows exporter is configured by WICD
- Closed
- links to