oc-mirror holds the updateService.yaml in the same directory with ImageContentSourcePolicy. When we apply the YAML files to the clusters as mentioned in https://docs.openshift.com/container-platform/4.13/installing/disconnected_install/installing-mirroring-disconnected.html#oc-mirror-updating-cluster-manifests_installing-mirroring-disconnected, updateService.yaml will be applied as well. The problem is for folks with a number of clusters, only one of those clusters needs OSUS installed so the updateService.yaml only needs to be applied once. In addition prior to apply the manifest, users should have the operator installed and switched to the osus project. So we are requesting to hold updateService.yaml in a separate sub directory and users can apply it as needs.

$ oc mirror version
Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.14.0-202303151415.p0.ga17d702.assembly.stream-a17d702", GitCommit:"a17d702aa852129f7c7beaa636e7e5cc8d3e687c", GitTreeState:"clean", BuildDate:"2023-03-15T14:45:33Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}

 

100%
 

1. Prepare the imageset-config file
$ cat imageset-config.yaml
kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v1alpha2
storageConfig:
  registry:
    imageURL: upshift.mirror-registry.qe.devcluster.openshift.com:5000/oc-mirror
    skipTLS: false
mirror:
  platform:
    channels:
    - name: candidate-4.11
      minVersion: 4.11.26
      maxVersion: 4.11.28
    graph: true

2. $ oc mirror --config=./imageset-config.yaml docker://upshift.mirror-registry.qe.devcluster.openshift.com:5000/oc-mirror
3.

$ ls oc-mirror-workspace/results-1680856624/
charts  imageContentSourcePolicy.yaml  mapping.txt  release-signatures  updateService.yaml
 

updateService.yaml is generated in a separate sub directory