To Reproduce Steps to reproduce the behavior:
A customer is trying to deploy a fresh RHOSP 18.0.15 environment. He is currently blocked by barbican-api pods consistently failing startup process and stuck in CrashLoopBackOff state.

From pod logs both httpd and barbican-api process were initialized properly, nontheless, probes fail consistently.

I have tried to check what is going on when pod is initialized and confirmed that processes are listening on proper port. So this looks like a problem in probing configuration, or some unusual issue affecting the sevice.

must-gather from affected environment is attached to the case.

Expected behavior
barbican-api pod is not blocked because of failed probes

Bug impact
Deployment is blocked, may be a wider problem affecting other customers as well.

Known workaround
None