You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we completed the switch to openshift-routes in our production environment and are quite happy with it.
However, we noticed that openshift-routes creates CertificateRequests - unlike cert-manager's ingress-shim which creates Certificates.
This has the unfortunate side-effect that we have no observability on these resources, because cert-manager's metrics endpoint exposes only metrics about Certificates (but not CertificateRequests, Orders, Challenges etc.). In practice this means that when one of the certificate requests get stuck (for many reasons, e.g. wrong DNS setup, order invalid, ...), we might not notice for a long time. :-(
Also wondering if switching to use Certificates instead of CertificateRequests is another feasible option. Maybe a bit more work but it would help with consistency as these differences come up.
Hello,
we completed the switch to openshift-routes in our production environment and are quite happy with it.
However, we noticed that openshift-routes creates
CertificateRequests
- unlike cert-manager's ingress-shim which createsCertificates
.This has the unfortunate side-effect that we have no observability on these resources, because cert-manager's metrics endpoint exposes only metrics about
Certificates
(but notCertificateRequests
,Orders
,Challenges
etc.). In practice this means that when one of the certificate requests get stuck (for many reasons, e.g. wrong DNS setup, order invalid, ...), we might not notice for a long time. :-(I see two possible ways to resolve this issue:
CertificateRequest
metrics directly in cert-managerI'm happy to discuss other ideas as well.
The text was updated successfully, but these errors were encountered: