lvms-disconnected-ImageSetConfig.adoc

Example ImageSetConfiguration CR for {lvms}

kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v1alpha2
archiveSize: 4 (1)
storageConfig: (2)
  registry:
    imageURL: example.com/mirror/oc-mirror-metadata (3)
    skipTLS: false
mirror:
  platform:
    channels:
    - name: stable-{product-version} (4)
      type: ocp
    graph: true (5)
  operators:
  - catalog: registry.redhat.io/redhat/redhat-operator-index:v{product-version} (6)
    packages:
    - name: lvms-operator (7)
      channels:
      - name: stable (8)
  additionalImages:
  - name: registry.redhat.io/ubi9/ubi:latest (9)
  helm: {}

1. Set the maximum size (in GiB) of each file within the image set.

2. Specify the location in which you want to save the image set. This location can be a registry or a local directory. You must configure the storageConfig field unless you are using the Technology Preview OCI feature.

3. Specify the storage URL for the image stream when using a registry. For more information, see Why use imagestreams.

4. Specify the channel from which you want to retrieve the {product-title} images.

5. Set this field to true to generate the OpenShift Update Service (OSUS) graph image. For more information, see About the OpenShift Update Service.

6. Specify the Operator catalog from which you want to retrieve the {product-title} images.

7. Specify the Operator packages to include in the image set. If this field is empty, all packages in the catalog are retrieved.

8. Specify the channels of the Operator packages to include in the image set. You must include the default channel for the Operator package even if you do not use the bundles in that channel. You can find the default channel by running the following command: $ oc mirror list operators --catalog=<catalog_name> --package=<package_name>.

9. Specify any additional images to include in the image set.