CSR for egress nodes were not approved automatically during certificate renewal

Solution Verified - Updated -


  • The renewal certs are not auto-approved only for the egress node where there are additional Egress IP's,
  • This issue occurs only when there are egress IP's assigned to node or the additional IP's(egress) changes compared to previously approved cert. we can see in logs that the SAN name check fails between current and new cert due to change in additional IP's.
  • Below is the error from machine-approver-controller-pod.log
Could not use current serving cert for renewal: CSR Subject Alternate Name values do not match current certificate
W0723 07:25:07.304126       1 csr_check.go:173] Current SAN Values: 


  • Red Hat OpenShift Container Platform
    • 4

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