Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8955

Add 'releasePath' parameter to ImageSetConfiguration platform block in oc-mirror v2

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • oc-mirror
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request
      Support custom target namespace and release path in oc-mirror v2 (feature parity with oc adm release mirror)

      2. What is the nature and description of the request?
      The request is to introduce a new configuration parameter, such as releasePath, within the platform block of the ImageSetConfiguration file (API mirror.openshift.io/v2alpha1).

      Currently, the oc-mirror v2 plugin forces a specific, hardcoded path structure on the destination registry. Users need the ability to specify a custom namespace and repository path for the release images in their disconnected registry (e.g., overriding the default to use something like openshift4/ocp-release).

      This enhancement would bring feature parity with the legacy oc adm release mirror command, which natively supports this via the --to and --to-release-image flags.

      Proposed Configuration Example:

      kind: ImageSetConfiguration
      apiVersion: mirror.openshift.io/v2alpha1
      mirror:
        platform:
          releasePath: "openshift4/ocp-release" # Requested custom path for the disconnected registry
          channels:
            - name: stable-4.20
              minVersion: 4.20.8
              maxVersion: 4.20.14
              shortestPath: true
              type: ocp

      3. Why does the customer need this?
      The customer is currently unable to migrate from the legacy oc adm release mirror tool to the newly supported oc-mirror v2 plugin because the new tool does not support their existing registry architecture.

      The disconnected registry is already structured with specific namespaces (e.g., registry.example.com/openshift4/ocp-release).

      Forcing a change to the target registry path structure to accommodate oc-mirror limitations would likely disrupt existing CI/CD pipelines, automated deployments, security scanning policies, and Role-Based Access Control (RBAC) rules established within the existing registry. Feature parity is required to ensure a smooth transition without architectural refactoring.

      4. List any affected packages or components.

      • oc-mirror plugin (specifically the v2 engine)
      • ImageSetConfiguration API definitions (mirror.openshift.io/v2alpha1)
      • Image mirroring and catalog building logic handling destination references

              rhn-support-mkalinin Marina Kalinin
              rhn-support-rludva Radomir Ludva
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                None
                None