As an OpenShift Windows admin, I want WMCO to copy over Windows-compatible container runtime settings onto my Windows nodes, so my cluster would function when disconnected from primary registries.

Description

This story covers copying over containerd config files, generated by WMCO, to each Windows instance in the cluster.

For new nodes, these files will be copied over to the instances on configuration, similar to how other config files (kublet conf, bootstrap kubeconfig, files from ignition, etc) are treated today. For existing nodes, the registry controller should SSH into each node and copy the generated config files, replacing any existing files.

The directory to save the generated registry config files is defined by WMCO – it should be the same as what it set for the containerd_conf.toml's `plugins."io.containerd.grpc.v1.cri".registry.config_path`.

The containerd daemon picks up the registry configuration without requiring restart so no further action required.

Acceptance Criteria

• Set features.operators.openshift.io/disconnected: true in CSV
• containerd configuration on Windows instances is updated based on any changes to mirrors defined in IDMS/ITMS
• images can be successfully pulled from the mirror registries without manual intervention
• disconnected CI job passes
• disconnected CI job is marked as required for master and release-4.16 branches
• engage docs team to update OCP docs with Windows specific info

QE testing

QE should ensure things work in two ways:

1. from a WMCO perspective
   • hosts.toml files are created properly on Windows nodes
   • when a user changes to mirrors defined in IDMS/ITMS resources, hosts.toml files are properly updated on Windows nodes
2. more importantly, from a cluster admin perspective
   • images are pulled from the mirrored location such that workloads can run
   • when a user changes to mirrors defined in IDMS/ITMS resources, images referenced in workloads are pulled according to the new config