-
Story
-
Resolution: Unresolved
-
Normal
-
openshift-4.19
-
Improvement
-
1
-
False
-
None
-
False
-
-
Enhancement
-
-
-
ShiftStack Sprint 267, ShiftStack Sprint 269
-
+
The cloud-credential-operator (CCO) consumes a root credential secret from kube-system / openstack-credentials and rolls it out to secrets in different namespaces, in response to CredentialsRequests CRs. We should modify CCO to start looking for a cacert field in this root credential secret and copying it to the generated secrets. This key name is chosen since it aligns with the expected secret key name used by components like CAPO and ORC.
- is depended on by
-
OSASINFRA-3730 Add CA bundle to root credential secret created by installer
-
- Code Review
-
-
OSASINFRA-3731 Consume CA bundle from CCO-provisioned credential secret in csi-operator, cluster-storage-operator
-
- Code Review
-
-
OSASINFRA-3732 Publish CA cert to well-known location in hypershift
-
- Code Review
-
-
OCPBUGS-50659 CAPO deployed by CAPI operator doesn't work with OpenStack self signed CA cert
-
- MODIFIED
-
- links to