Changes in Twistlock policies cause networking failures in Openshift 4
Issue
- Multiple pods go into CrashLoopBackOff
- pods fail with Liveness probe failed
- pods fail with Readiness probe error
- pod network connectivity checks are showing connection refused
- Certain pods remain Running, but have containers that are not Ready
- pods have a Liveness probe configured, but not a Readiness probe
Environment
- Red Hat OpenShift Container Platform
- 4
- Running with Twistlock application
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
