-
Epic
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
None
-
Peerpodconfig Controller is removed from cloud-api-adaptor
-
BU Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
67% To Do, 0% In Progress, 33% 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
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
- Documentation update HCIDOCS-529
- Tests
- is documented by
-
HCIDOCS-529 Peer pods limit moved to peer pods CM
- New
- is related to
-
KATA-3466 Test cloud-api-adapter 0.0 with OpenShift Sandboxed Containers 1.8.0 and Kata Containers 3.11
- New