-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
BU Product Work
-
5
-
False
-
False
-
OCPSTRAT-526 - Cloud Controller Managers: Final Testing and GA tasks - Phase 1
-
Undefined
-
-
CLOUD Sprint 207, CLOUD Sprint 208, CLOUD Sprint 209, CLOUD Sprint 210, CLOUD Sprint 211, CLOUD Sprint 212
User Story
As a userĀ of Windows Containers I want my windows nodes to be configured by the Cloud Node Manager so that my workloads will continue to run after the migration to out of tree cloud providers
Background
Once we move to out of tree cloud providers, certain platforms (Azure/Azure Stack Hub) require a separate agent (Cloud Node Manager) to run on each Node. This node manager is responsible for initialising each Node when the kubelet registers it with the API. For example it is responsible for reading cloud provider specific information and adding this to the Node as an annotation
Steps
- Add a new Windows service to WMCO on Azure/Azure Stack to deploy the node manager
- Ensure we are building/ shipping Windows Go binaries for the Azure/Azure Stack CNM
Stakeholders
- Cluster Infra
- Windows team
Definition of Done
- CNM runs on Azure/Azure Stack when windows nodes are included in the cluster and external cloud providers are enabled
- Docs
- N/A
- Testing
- Ensure when deployed on Azure, with out of tree cloud providers enabled, windows nodes successfully join the cluster
- blocks
-
WINC-616 Adjust kubelet cloud flags based on cloud provider
- Closed
- links to