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
From time to time we see issues after node reboot - admission-webhook stays in CrashLoopBack, the logs complain that the mutatingwebhookconfiguration is already there. Removing the existing configuration solves the problem:
Probable reason:
It is related to thing that admission webhook is using self signed cert and when admission webhook restarts it generates a new cert that is not eual to cert from the registered k8s configuraiton
The text was updated successfully, but these errors were encountered:
From time to time we see issues after node reboot - admission-webhook stays in CrashLoopBack, the logs complain that the mutatingwebhookconfiguration is already there. Removing the existing configuration solves the problem:
Probable reason:
It is related to thing that admission webhook is using self signed cert and when admission webhook restarts it generates a new cert that is not eual to cert from the registered k8s configuraiton
The text was updated successfully, but these errors were encountered: