-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
ShiftStack Sprint 267, ShiftStack Sprint 270, ShiftStack Sprint 271
-
3
-
+
-
In Progress
-
Bug Fix
-
CAPO deployed by cluster-capi-operator will now work correctly in deployments using self-signed certificates.
-
None
-
None
-
None
-
None
In TechPreviewNoUpgrade, CAPI Operator is deployed and takes care of deploying CAPO.
However, we have seen in CI that when the OpenStack endpoints use a self signed CA certificate, CAPO complains about TLS:
2025-02-12T21:20:57Z ERROR Reconciler error {"controller": "clusteroperator", "controllerGroup": "config.openshift.io", "controllerKind": "ClusterOperator", "ClusterOperator": {"name":"cluster-api"}, "namespace": "", "name": "cluster-api", "reconcileID": "119878d6-e7b6-40d0-8f0d-2b88ace46cde", "error": "creating OpenStack provider scope: providerClient authentication err: Get \"https://38.102.83.27:13000/\": tls: failed to verify certificate: x509: certificate signed by unknown authority"}
- depends on
-
OSASINFRA-3657 Sync CA bundle from root credential to generated credentials
-
- Closed
-
