-
Spike
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
5
-
False
-
None
-
False
-
-
Upstream issue: https://github.com/argoproj/argo-cd/issues/3539
When we add a tls cert for helm repo, the ArgoCD repo server does not read this tls certificate and gives an error `x509: certificate signed by unknown authority`.
Expected behavior:
ArgoCD repo server should accept the tls certificate when the repo itself is configured.
Current Workaround:
- https://docs.openshift.com/container-platform/4.11/operators/admin/olm-configuring-proxy-support.html#olm-inject-custom-ca_olm-configuring-proxy-support.
- https://github.com/argoproj/argo-cd/issues/3539#issuecomment-743333648
Acceptance Criteria:
- Find the root cause of why argocd repo server is not able to read the tls certificates
- Add the fix to the issue comments and create a PR upstream
- is related to
-
GITOPS-1482 Argo CD repo server doesn't read TLS certs for helm repo
- Closed
- relates to
-
RFE-3808 Configuration of ArgoCD Notifications and Certificates
- Accepted