Description of problem:

Deploy logging stack via operator, make sure the logging stack works well. Then scale down CLO to 0, delete mater-certs secret, scale up CLO to 1. After doing these, master-certs secrte is regenerated, the secret curator, fluentd, kibana and elasticsearch are changed, but the kibana pod isn't updated. Log into kibana console, the status is RED.

Logs in the kibana pod:
{"type":"log","@timestamp":"2019-12-10T06:48:00Z","tags":["warning","elasticsearch","admin"],"pid":227,"message":"Unable to revive connection: https://elasticsearch.openshift-logging.svc.cluster.local:9200/"}
{"type":"log","@timestamp":"2019-12-10T06:48:00Z","tags":["warning","elasticsearch","admin"],"pid":227,"message":"No living connections"}
{"type":"log","@timestamp":"2019-12-10T06:48:02Z","tags":["warning","elasticsearch","admin"],"pid":227,"message":"Unable to revive connection: https://elasticsearch.openshift-logging.svc.cluster.local:9200/"}
{"type":"log","@timestamp":"2019-12-10T06:48:02Z","tags":["warning","elasticsearch","admin"],"pid":227,"message":"No living connections"}

Then delete kibana pod, wait until new kibana pod start, try to access kibana console via browser, get error:
Application is not available

The application is currently not serving requests at this endpoint. It may not have been started or is still starting.

deleting route/kibana then wait for CLO to create a new kibana/route can resolve this problem. 


Version-Release number of selected component (if applicable):
ose-cluster-logging-operator-v4.3.0-201912091517

How reproducible:
Always

Steps to Reproduce:
1.deploy clusterlogging
2.scale down CLO replicas to 0
3.delete secret/master-certs
4.scale up CLO
5.wait until all pods running, log into kibana console

Actual results:


Expected results:


Additional info: