1.  when following RH-SSO Openshift Documentation Instructions:

oc create -f sso75-presistent-reencrypt-template-file.yaml

$ oc get pods
NAME READY STATUS RESTARTS AGE
sso-1-deploy 0/1 Error 0 44m
sso-postgresql-1-92jgh 1/1 Running 0 36m
sso-postgresql-1-deploy 0/1 Completed 0 36m
sso-postgresql-enable-ssl-1-build 0/1 Completed 0 44m

SSO deployment pod is failing due to the fact that SSO PostgreSQL database pod is not yet up-and-ruuning.

2.  What is needed
Therefore within the template a dependency should be introduced so that SSO pod does not start before PostgreSQL pod is up.

This will avoid customer not being able to deploy RH-SSO on Openshift with documented solution not working.

3. Current work-around

The current work-around is to follow KCS:  

https://access.redhat.com/solutions/6429401

 
This KCS mainly describes:

-Set SSO replica to 0 in Yaml file
-Set Health check probes timeout to 300s
-Wait for PostgreSQL DB to be up-and-running before starting SSO pod.