Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-1757

post-merge testing: Azure: Publish and leverage CoreOS Image coming from a trusted source

XMLWordPrintable

    • Trusted Image Source CoreOS
    • True
    • False
    • Red
    • To Do
    • OCPSTRAT-859 - Support custom RHCOS image location for Azure (Phase II)
    • OCPSTRAT-859Support custom RHCOS image location for Azure (Phase II)
    • 100
    • 100% 100%
    • Undefined
    • Hide

      Awaiting feedback on the scope of work and linking of other existing epics for the other teams involved in this deliverable (e.g. RHCOS and the release teams).

      March 19 2024 - We've decided to limit the scope of this epic to the ARO use-case but document the feature so it can also be used by customers with self-managed installs. Using marketplace images by default in the Installation process is out of the scope for 4.16. QE has already validated the work via CORS-2722. We are only missing docs.

      Show
      Awaiting feedback on the scope of work and linking of other existing epics for the other teams involved in this deliverable (e.g. RHCOS and the release teams). March 19 2024 - We've decided to limit the scope of this epic to the ARO use-case but document the feature so it can also be used by customers with self-managed installs. Using marketplace images by default in the Installation process is out of the scope for 4.16. QE has already validated the work via CORS-2722 . We are only missing docs.

       

      Epic Goal

      • As a customer, I need to make sure that the CoreOS image I leverage are coming from a trusted source. 

      Why is this important?

      • As an ARO service, to make sure that the service is secure and gets the certification needed
      • As an OCP customer, I want to ensure that my images come from a trusted source 

      Scenarios

      1. As a managed Service, we need to be able to trust the source of the image and a public blob is not considered a trusted source for the image(s) 

      Acceptance Criteria

      CoreOS Image is pushed into Azure patner portal and the azure partner portal is used as a source for the install

      Previous Work (Optional):

      1. https://github.com/openshift/installer/pull/4865

       

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

            rdossant Rafael Fonseca dos Santos
            jboutaud@redhat.com Jerome Boutaud
            Jinyun Ma Jinyun Ma
            Votes:
            2 Vote for this issue
            Watchers:
            25 Start watching this issue

              Created:
              Updated:
              Resolved: