Uploaded image for project: 'Cluster Integration and Delivery'
  1. Cluster Integration and Delivery
  2. CLID-179

As a user I want the kubevirt coreos container to be available in the oc-mirror release payload so that it can be accessed and installed in an air-gapped environment

XMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      • All unit tests pass (80% coverage)
      • KubeVirt container included into release payload 
      • Documentation approved by docs team
      • All tests QE approved 
      • Well documented README/HOWTO/OpenShift documentation
      Show
      All unit tests pass (80% coverage) KubeVirt container included into release payload  Documentation approved by docs team All tests QE approved  Well documented README/HOWTO/OpenShift documentation
    • OCPSTRAT-1484 - OC Mirror to include the HyperShift KubeVirt CoreOS container
    • ---
    • ---
    • CLID Sprint 259
    • 100% (High)
    • No

      Overview

      Refer to RFE-5468

      The coreos image is needed to ensure seamless deployment of HyperShift KubeVirt  functionality in disconnected/air-gapped environments.

      Solution

      This story will address this issue, in that oc-mirror will include the cores kubevirt container image in the release payload

      The image is found in the file release-manifests/0000_50_installer_coreos-bootimages.yaml

      A field kubeVirtContainer (default false) will be added to the current v2 imagesetconfig and if set to true, the release collector will have logic to read and parse the yaml file correctly to extract and add the "DigestRef" (digest) to the release payload

       

            luzuccar@redhat.com Luigi Mario Zuccarelli
            luzuccar@redhat.com Luigi Mario Zuccarelli
            Rama Kasturi Narra Rama Kasturi Narra
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: