Verified in clusterlogging.4.3.14-202004231410 1. check kibana status #oc get route kibana -o json |jq '.spec.tls.caCertificate' #Access the kibana #oc get pods NAME READY STATUS RESTARTS AGE cluster-logging-operator-74b5785596-5p8rx 1/1 Running 0 10m curator-1587714600-qq77f 0/1 Completed 0 4m4s elasticsearch-cdm-cs4flf8z-1-59dbfdc784-n4hl6 2/2 Running 0 8m31s elasticsearch-cdm-cs4flf8z-2-7d7b4b84b-zs65m 2/2 Running 0 8m31s elasticsearch-cdm-cs4flf8z-3-67c8785f5c-pd8wn 2/2 Running 0 8m31s fluentd-4pp9z 1/1 Running 1 5h17m fluentd-bkfzf 1/1 Running 0 5h17m fluentd-hj9jb 1/1 Running 0 5h17m fluentd-nbtk9 1/1 Running 1 5h17m fluentd-sm2nz 1/1 Running 0 5h17m fluentd-strtp 1/1 Running 0 5h17m kibana-67f5f6774b-bqt22 2/2 Running 0 9m18s 2.Refresh the ca in cluster-logging-operators #oc exec $clo_pod -- rm -rf /tmp/ocp-clo #oc delete deployment cluster-logging-operator #oc exec $clo_pod -- rm -rf /tmp/ocp-clo 3 Verify the pod/kibana was restarted. the route/kibana was updated. and the kibana route can be accessable.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:1529