Custom wildcard router certificates are not getting updated with the new CA

Solution Verified - Updated -

Issue

Custom wildcard router certificates were not getting updated with the new CA as the applications were still using the certificates signed by the old CA.

# echo|openssl s_client -servername grafana-openshift-monitoring.apps.example.local -connect grafana-openshift-monitoring.apps.example.local:443 2>/dev/null|openssl x509 -noout -dates

 notBefore=Dec  4 12:58:16 2018 GMT
 notAfter=Apr 14 08:19:53 2020 GMT
# openssl x509 -enddate -noout -in ca.crt 

  notAfter=Nov 27 08:40:08 2025 GMT

Environment

  • Red Hat OpenShift Container Platform [OCP]
    • v3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content