Hi Team,

We have deployed ONAP frankfurt release on Kubernetes. Currently OOF-HAS-* containers are failing to initialize. 

Inspecting the pod, it seems that some of the init-containers are failing to complete with error:

oof-has-api-has-sms-readiness:
Container ID:
Image: oomk8s/readiness-check:2.0.2
Image ID:
Port: <none>
Host Port: <none>
Command:
sh
-c
resp="FAILURE"; until [ $resp = "200" ]; do resp=$(curl -s -o /dev/null -k --write-out %{http_code} https://aaf-sms.onap:10443/v1/sms/domain/has/secret); echo $resp; sleep 2; done

Please suggest how to approach the problem further