After the removal of twistlock application, experiencing RHOCP 4.x login fail and authentication operator is in the degraded state

Solution Verified - Updated -

Issue

  • After the removal of twistlock application, RHOCP login fails on the command line and on the console.

  • After the removal of twistlock application, the authentication operator is in a degraded state.

  • Kube-apiserver is giving the following error when we try to log in.

    failed calling webhook "validating-webhook.twistlock.com": Post 
https://defender.twistlock.svc:443/3n9i02e6jbn4ol6h7dhcdpcclumz?timeout=30s: no endpoints available for service 
"defender"

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