As an OpenShift cluster administrator I would like to have the Kubernetes components on Windows nodes upgraded when new Kubernetes versions or patch versions are released.

Description

The upgrade process for BYOH nodes will be different to that of upgrading Windows nodes added using a MachineSet in an IPI cluster. In the MachineSet case, Machines are deleted in lieu of upgrading where as here the Windows instances will have to be reconfigured. It should also be decided if the upgrade process, deconfigure and reconfigure, should occur if a BYOH node is in a not ready state. This decision can be partly based around what the RHEL BYOH process is like, but that should not be the only factor.

Engineering details

WMCO will handle the reconfiguration process and will include:

• Drain and cordon the node
• Stop, copy over new binaries and update:
  • Monitoring and logging services
  • kube-proxy service
  • hybrid-overlay-node service
  • kubelet service
• Uncordon the node

Acceptance criteria

• WMCO handles upgrading of BYOH instances
• e2e test to exercise this feature