As an OpenShift developer, I want to ensure change in private key for WMCO would not result in Windows VM deletion and recreation

Acceptance criteria:

• A PR or story to how to handle changes to private key

Engineering details:
An easy implementation would be:

• Once secret controller in WMCO receives notification of private key change instead of checking for key SHA on the node object(this is WIP), we login to the Windows VM and replace the SSH key with the new key. Rest of the configuration.

Another good thing to think about, we are actually treading into day-2 configuration of Windows VMs and not going with immutability. While this is not bad, I think replacing keys etc on the Windows VM is the responsibility of WMCB, should we make WMCB a daemon which watches for all the VM related configuration and let it handle these types of scenarios.