What is desired
The configuration file for oc mirror needs to be assembled by the user. Some users may have running clusters that they simply want to clone. oc mirror should have a feature that allows to create mirroring configuration that corresponds to a cluster that it is being pointed at. The result is a mirror that can be used to run that same cluster disconnected from public registries.
What you expected to happen?
oc mirror would make use of the oc context that it is running in as a plugin to connect to a particular cluster. It would need sufficient permissions to introspect the cluster and survey the following data points:
- cluster version running
- installed CatalogSources / operator catalogs
- installed operators, including their versions and channels
- bonus points: determining installed helm releases and their source charts
Duplicate results need to be removed from the above sets.
The output of the survey should be a ready-to-run mirror configuration file that is stored on disk or sent to stdout for reuse.
What is desired
The configuration file for
oc mirrorneeds to be assembled by the user. Some users may have running clusters that they simply want to clone.oc mirrorshould have a feature that allows to create mirroring configuration that corresponds to a cluster that it is being pointed at. The result is a mirror that can be used to run that same cluster disconnected from public registries.What you expected to happen?
oc mirrorwould make use of theoccontext that it is running in as a plugin to connect to a particular cluster. It would need sufficient permissions to introspect the cluster and survey the following data points:Duplicate results need to be removed from the above sets.
The output of the survey should be a ready-to-run mirror configuration file that is stored on disk or sent to stdout for reuse.