provide support for 3rd party tls certificates about gitops-operator HOT 7 CLOSED

For anyone who upgraded/was automatically upgraded from v1.2.1 and had your route break, remove the destinationCACertificate from spec.server.route.tls in your ArgoCD resource.

from gitops-operator.

@davidkarlsen #224 (comment)

from gitops-operator.

Using service-servicing certificates is a good start, and it would be even better if the route could use re-encrypt with the default ingress certificate.

from gitops-operator.

Using service-servicing certificates is a good start, and it would be even better if the route could use re-encrypt with the default ingress certificate.

With the upcoming release of v1.3, if you set the route's termination policy to reencrypt, the route's backend (argocd-server) will automatically be configured with a certificate from service CA, which is trusted by the route's controller. The user facing endpoint would use the certificate that you have configured for the route.

Also, if you don't set route's policy to reencrypt (e.g. to passthrough), you can supply a user provided cert/key combination to the TLS secret argocd-server-tls, which will then be used by the argocd-server endpoint, which in case of passthrough would be the user facing endpoint.

Does that satisfy both of your use cases?

from gitops-operator.

@jannfis that sounds perfect - when is 1.3 planned for?

from gitops-operator.

@davidkarlsen #224 (comment)

🤦 sorry for my short time memory :) looking forward to 4.9 :)

from gitops-operator.

It's working as expected with version 1.3 so I will close the ticket, thank you for your support!

from gitops-operator.