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

Peerpodconfig Controller is removed from cloud-api-adaptor

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • None
    • None
    • None
    • Peerpodconfig Controller is removed from cloud-api-adaptor
    • BU Product Work
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 0% To Do, 25% In Progress, 75% Done
    • Yes
    • 0
    • 0

      Peerpodconfig Controller is removed from upstream cloud-api-adaptor and the per node peer-pods limit is now a config item in the peer-pods-cm ConfigMap

       

      Ref: https://github.com/confidential-containers/cloud-api-adaptor/pull/2027 

      https://github.com/confidential-containers/cloud-api-adaptor/blob/main/src/cloud-api-adaptor/install/overlays/aws/kustomization.yaml#L38

      https://github.com/confidential-containers/cloud-api-adaptor/blob/main/src/cloud-api-adaptor/install/overlays/azure/kustomization.yaml#L44

       

      This feature is part of CoCo 0.10.0 and requires some work downstream:

      • Removal of peerpodconfig controller from the OSC operator
      • Handling 1.7.0 to 1.8.0 upgrades
        • Automatically populating the peer-pods-cm configMap entry (PEERPODS_LIMIT_PER_NODE)  based on the peerpodConfig CRD entry if present
        • Deleting the peerpodConfig CRD

              Unassigned Unassigned
              jrope Julien ROPE
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: