RH SSO Pod not restarted when Readiness probe failed multiple times
Issue
During one test(we already run multiple times without issues) one of the two instances(keycloak-1) failed multiple time the readiness probe[attachment: readiness_probe_failed.PNG] our expectation here is that while the keycloak-1 is rebooting the instance keycloak-0 continue to provide the service but for some reason the instance is stuck and not automatically rebooted[attachment: topology.PNG]
Environment
- RH SSO 7.5.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.