이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 4. Updating cluster logging
After updating the OpenShift Container Platform cluster from 4.2 to 4.3, you must then upgrade cluster logging from 4.2 to 4.3.
4.1. Updating cluster logging
After updating the OpenShift Container Platform cluster, you can update cluster logging from 4.2 to 4.3 by updating the subscription for the Elasticsearch Operator and the Cluster Logging Operator.
Changes introduced by the new log forward feature modified the support for out_forward starting with the OpenShift Container Platform 4.3 release. In OpenShift Container Platform 4.3, you create a ConfigMap to configure out_forward. Any updates to the secure-forward.conf section of the Fluentd ConfigMap are removed.
If you use the out_forward plug-in, before updating, you can copy your current secure-forward.conf section from the Fluentd ConfigMap and use the copied data when you create the secure-forward ConfigMap.
Prerequisites
- Update the cluster from 4.2 to 4.3.
Make sure the cluster logging status is healthy:
-
All Pods are
ready. - Elasticsearch cluster is healthy.
-
All Pods are
-
Optionally, copy your current
secure-forward.confsection from the Fluentd ConfigMap for use if you want to create thesecure-forwardConfigMap. See the note above.
Procedure
Update the Elasticsearch Operator:
-
From the web console, click Operators
Installed Operators. -
Select the
openshift-loggingproject. - Click the Elasticsearch Operator.
-
Click Subscription
Channel. - In the Change Subscription Update Channel window, select 4.3 and click Save.
Wait for a few seconds, then click Operators
Installed Operators. The Elasticsearch Operator is shown as 4.3. For example:
Elasticsearch Operator 4.3.0-201909201915 provided by Red Hat, Inc
-
From the web console, click Operators
Update the Cluster Logging Operator:
-
From the web console, click Operators
Installed Operators. -
Select the
openshift-loggingProject. - Click the Cluster Logging Operator.
-
Click Subscription
Channel. - In the Change Subscription Update Channel window, select 4.3 and click Save.
Wait for a few seconds, then click Operators
Installed Operators. The Cluster Logging Operator is shown as 4.3. For example:
Cluster Logging 4.3.0-201909201915 provided by Red Hat, Inc
-
From the web console, click Operators
Check the logging components:
Ensure that the Elasticsearch Pods are using a 4.3 image:
$ oc get pod -o yaml -n openshift-logging --selector component=elasticsearch |grep 'image:' image: registry.redhat.io/openshift4/ose-logging-elasticsearch5:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-oauth-proxy:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-elasticsearch5:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-oauth-proxy:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-elasticsearch5:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-oauth-proxy:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-elasticsearch5:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-oauth-proxy:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-elasticsearch5:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-oauth-proxy:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-elasticsearch5:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-oauth-proxy:v4.3.0-202001081344
Ensure that all Elasticsearch Pods are in the Ready status:
$ oc get pod -n openshift-logging --selector component=elasticsearch NAME READY STATUS RESTARTS AGE elasticsearch-cdm-1pbrl44l-1-55b7546f4c-mshhk 2/2 Running 0 31m elasticsearch-cdm-1pbrl44l-2-5c6d87589f-gx5hk 2/2 Running 0 30m elasticsearch-cdm-1pbrl44l-3-88df5d47-m45jc 2/2 Running 0 29m
Ensure that the Elasticsearch cluster is healthy:
oc exec -n openshift-logging -c elasticsearch elasticsearch-cdm-1pbrl44l-1-55b7546f4c-mshhk -- es_cluster_health { "cluster_name" : "elasticsearch", "status" : "green", ....Ensure that the logging collector Pods are using a 4.3 image:
$ oc get pod -n openshift-logging --selector logging-infra=fluentd -o yaml |grep 'image:' image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-fluentd:v4.3.0-202001081344
Ensure that the Kibana Pods are using a 4.3 image:
$ oc get pod -n openshift-logging --selector logging-infra=kibana -o yaml |grep 'image:' image: registry.redhat.io/openshift4/ose-logging-kibana5:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-oauth-proxy:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-logging-kibana5:v4.3.0-202001081344 image: registry.redhat.io/openshift4/ose-oauth-proxy:v4.3.0-202001081344
Ensure that the Curator CronJob is using a 4.3 image:
$ $ oc get CronJob curator -n openshift-logging -o yaml |grep 'image:' image: registry.redhat.io/openshift4/ose-logging-curator5:v4.3.0-202001081344
