Satellite updated the configuration for the local Container Runtime

[Vad1mo]

In order for the workloads (container runtime) to know from which container registry artifacts should be fetched. Satellites should have the possibility to update the configuration for different runtimes.

From the user perspective, the process should work manually and automated.

### Manually

• The user can patch the runtime calling harbor-satellite patach-runtime
• Instead of patching the config of the runtime, the user can dump the changes to the command line so that the user can apply those changes manually on the same or other system.

Automated

• In the config of satellite, the satellite operator can decide to automatically patch and verify the patch once the satellite starts.

Supported Runtimes

1. Containerd
2. CRI-O
3. tbd.

Requirements

• Support updating Containerd and CRI-O
• Dump of a container runtime config file that can be used as as in input on another remote machine.

Out of Scope

Updating other container runtimes on different machines.