-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When deploying the telco-hub with the backup-recovery and the cert-manager (the later not part of RDS yet) components enabled, we may see below errors in ArgoCD.
The Kubernetes API could not find <Custom Resource> for requested resource CR. Make sure the "<Custom Resource>" CRD is installed on the destination cluster.
Version-Release number of selected component (if applicable):
4.20
How reproducible:
Always (when deploying the mentioned components are enabled)
Steps to Reproduce:
1. Deploy the telco-cluster as defined in https://github.com/openshift-kni/telco-reference/tree/main 2. Enable mentioned components in your kustomize
Actual results:
ArgoCD shows some errors when deploying the telco-hub.
Expected results:
Smooth and predictable roll out of telco-hub resources via ArgoCD.
Additional info:
