After the oom standard configuration was committed for https://jira.onap.org/browse/OOM-740, the kibana.yml config file was not mounted correctly so kibana failed to start. Also the new kibana readiness/liveness settings were not detecting when kibana is ready or live.

Kibana pod did not progress to Running status and it was restarted continuously.

Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 4m default-scheduler Successfully assigned onap-log-kibana-775999b59b-nsns4 to onap-1
Normal SuccessfulMountVolume 4m kubelet, onap-1 MountVolume.SetUp succeeded for volume "localtime"
Normal SuccessfulMountVolume 4m kubelet, onap-1 MountVolume.SetUp succeeded for volume "onap-log-kibana"
Normal SuccessfulMountVolume 4m kubelet, onap-1 MountVolume.SetUp succeeded for volume "default-token-ngntx"
Normal Pulling 4m kubelet, onap-1 pulling image "oomk8s/readiness-check:1.1.0"
Normal Pulled 3m kubelet, onap-1 Successfully pulled image "oomk8s/readiness-check:1.1.0"
Normal Created 3m kubelet, onap-1 Created container
Normal Started 3m kubelet, onap-1 Started container
Warning Unhealthy 2m (x3 over 2m) kubelet, onap-1 Liveness probe failed: Get http://10.42.68.250:5601/: dial tcp 10.42.68.250:5601: getsockopt: connection refused
Normal Pulling 2m (x2 over 3m) kubelet, onap-1 pulling image "docker.elastic.co/kibana/kibana:5.5.0"
Warning Unhealthy 2m (x6 over 2m) kubelet, onap-1 Readiness probe failed: Get http://10.42.68.250:5601/: dial tcp 10.42.68.250:5601: getsockopt: connection refused
Normal Killing 2m kubelet, onap-1 Killing container with id docker://log-kibana:Container failed liveness probe.. Container will be killed and recreated.