Multiple Cluster Operators are degraded with failed to call webhook error in RHOCP4

Solution Verified - Updated -

Issue

The RHOCP cluster is down as multiple critical Cluster Operators (CO) such as authentication,etcd,kube-apiserver, kube-controller-manager, kube-scheduler, machine-config are degraded with the below error.

$ oc get co
<..>
etcd                                       4.12.9    True        False         True       660d    GuardControllerDegraded: Unable to apply pod etcd-guard-example.com changes: Internal error occurred: failed calling webhook "example-service.test.svc": failed to call webhook: Post "https:/example-service.test.svc:19090/mutate?timeout=10s": service "example-service" not found

kube-apiserver                             4.12.9    True        False         True       660d    GuardControllerDegraded: Unable to apply pod kube-apiserver-guard-example.com changes: Internal error occurred: failed calling webhook "example-service.test.svc": failed to call webhook: Post "https://example-service.test.svc:19090/mutate?timeout=10s": service "example-service" not found
<..>

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 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