-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
3
-
None
-
None
-
None
Once https://issues.redhat.com/browse/OCPCLOUD-3327 is done we need to update CCAPIO to no longer rely on transport config maps. Currently, we do that only in one place - VAPs.
We need to: un-transport config-map -ify the VAPs, and splitting them out to their own files. Currently we apply platform specific VAPs only to that platform, e.g CAPA VAPs only get deployed on AWS.
To replicate this behaviour we need platform specific profiles that will also live in CCAPIO:
Structure CCAPIO's image like: /capi-operator-manifests/ default/ metadata.yaml # ocpPlatform: "" (no platform = always install) manifests.yaml # core/shared VAPs aws/ metadata.yaml # ocpPlatform: AWS manifests.yaml # AWS-specific VAPs gcp/ metadata.yaml # ocpPlatform: GCP manifests.yaml # GCP-specific VAPs ...
Steps:
Break out transport config maps
write kustomise to include them in the image, writing to the correct profiles
update VAP unit tests to deal with the new structure.
- depends on
-
OCPCLOUD-3327 Update manifests-gen to support image substitution
-
- In Progress
-
- is depended on by
-
OCPCLOUD-3328 Update all providers to use new manifests-gen
-
- To Do
-
- links to