Is your feature request related to a problem? Please describe.
The ArgoCD console is setup with a default self-signed cert that is not trusted by web browser.
Firefox, in particular, has stopped accepting those types of certs altogether.
Describe the solution you'd like
The ArgoCD console should reuse the default ingress cert for the platform.
Describe alternatives you've considered
The repo could have instructions to prereq the ArgoCD TLS cert in the openshift-gitops namespace, but that is not as convenient as having the git repo contain the synchronization hook for it.
Is your feature request related to a problem? Please describe. The ArgoCD console is setup with a default self-signed cert that is not trusted by web browser. Firefox, in particular, has stopped accepting those types of certs altogether.
Describe the solution you'd like The ArgoCD console should reuse the default ingress cert for the platform.
This needs Rd Hat to fix this issue: https://github.com/redhat-developer/gitops-operator/issues/297
Describe alternatives you've considered The repo could have instructions to prereq the ArgoCD TLS cert in the openshift-gitops namespace, but that is not as convenient as having the git repo contain the synchronization hook for it.
Additional context Red Hat implementation note: Configure the Argo CD route with Edge or Reencrypt TLS termination in Red Hat OpenShift GitOps
Note that the declarative solution in Configure the Argo CD route with Edge or Reencrypt TLS termination in Red Hat OpenShift GitOps makes the internal route unsecure, exposing it to eventual