-
Bug
-
Resolution: Done
-
Major
-
1.12.0, 1.12.2
-
3
-
False
-
None
-
False
-
-
-
GitOps Crimson - Sprint 3258, GitOps Crimson - Sprint 3259, GitOps Crimson - Sprint 3260, GitOps Crimson - Sprint 3261
Description of problem:
Adding a self-signed TLS cert for the for the ApplicationSet Gitlab SCM Providerdoesn't work as expected in Gitops
Workaround:
Client have to use insecure=true in the ApplicationSet configs
Steps to Reproduce:
As described in [1] and validated with [2], the `scmRootCAConfigMap` must be set in the ArgoCD CR, e.g.:
spec: applicationSet: scmRootCAConfigMap: my-gitlab-scm-tls-cert
- The certificate is only mounted if the name of the scmRootCAConfigMap is “argocd-appset-gitlab-scm-tls-certs-cm”.
- Then the certificate is created, but as a file in rootPath /app/tls/scm/cert/ with filename according to the key value in the CM.
However, the openshift-gitops-applicationset-controller expects the certificate file as /app/tls/scm/cert and fails with:
level=error msg=“error reading certificate from file ‘/app/tls/scm/cert’, proceeding without custom rootCA : read /app/tls/scm/cert: is a directory”
Prerequisites (if any, like setup, operators/versions):
OCP: 4.14.19
openshift-gitops-operator.v1.12.2
- is duplicated by
-
GITOPS-5113 Fix TLS cert name for the for the ApplicationSet Gitlab SCM
-
- Closed
-
- links to
-
RHEA-2024:137049 Errata Advisory for OpenShift GitOps v1.14.0