Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-2870

Enable CoCo featuregate in OSC operator for techpreview

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: High High
    • OSC 1.7.0
    • None
    • None
    • None
    • Enable CoCo featuregate in OSC operator for techpreview
    • BU Product Work
    • L
    • False
    • None
    • False
    • Not Selected
    • To Do
    • KATA-2416 - Enable Confidential Containers using the OpenShift sandboxed containers operator
    • 0% To Do, 0% In Progress, 100% Done
    • Yes
    • 0
    • 0

      Epic Goal

      • Customers are able to run confidential workloads on enabled Azure instances and IBMz, through PeerPods. The OSC operator must enable this. Both SEV/SNP and TDX are in scope. Target platforms are Azure and IBMz.

      Why is this important?

      • Enables users to deploy confidential containers 

      Scenarios

      1. Cluster administrator able to configure coco functionality using the OSC operator.
      2. Users can deploy confidential pods using a specific runtime class.

      Acceptance Criteria 

      (The Epic is complete when...)

      1. Ability to configure CoCo functionality in a new OSC install
      2. Ability to configure CoCo functionality in an existing OSC install
      3. Ability to remove CoCo functionality from an existing OSC install
      4. Operator writes the expected values to the podvm config maps.
      5. Operator writes the expected values to the peer-pods config map.

       

            rh-ee-cconte Camilla Conte
            bpradipt Pradipta Banerjee
            Victor Voronkov
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: