Document URL: https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html-single/logging/index#cluster-logging-deploying Section Number and Name: 3.1. Installing OpenShift Logging using the web console Verify the install 3.3. Installing OpenShift Logging using the CLI Verify the installation by listing the pods in the openshift-logging project 4.2.2. Viewing logging collector pods 4.8.1. Moving OpenShift Logging resources Verification 10.1. Updating from cluster logging in OpenShift Container Platform 4.6 or earlier to OpenShift Logging 5.x Verify that the log collector is updated to 5.0 or 5.x: 12.1.1. Viewing the status of the Red Hat OpenShift Logging Operator Describe the issue: The pods running the fluentd collector are no more named fluentd. They were renamed to collector Suggestions for improvement: Rename the pod names to collector Additional information: # oc get ds -n openshift-logging NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE collector 6 6 6 6 6 kubernetes.io/os=linux 3d19h # oc get pod -n openshift-logging NAME READY STATUS RESTARTS AGE cluster-logging-operator-78dcf484f4-g67np 1/1 Running 0 3d11h collector-94tcb 2/2 Running 2 3d18h collector-95zzf 2/2 Running 2 3d18h collector-fpcjk 2/2 Running 2 3d18h collector-lsqjd 2/2 Running 2 3d18h collector-px7px 2/2 Running 2 3d18h collector-ztxlk 2/2 Running 2 3d18h elasticsearch-cdm-e3kyu02l-1-7dc84b895d-6ml88 2/2 Running 0 3d17h elasticsearch-cdm-e3kyu02l-2-588db4cdcf-74cn8 2/2 Running 0 3d11h elasticsearch-cdm-e3kyu02l-3-6fb5fb98bd-vbbdc 2/2 Running 0 3d11h elasticsearch-im-app-27353340--1-rtrct 0/1 Completed 0 2m3s elasticsearch-im-audit-27353340--1-jgb5x 0/1 Completed 0 2m3s elasticsearch-im-infra-27353340--1-fckvk 0/1 Completed 0 2m3s kibana-6c6b8df449-lmkbx 2/2 Running 0 3d11h
All open BZs in this project will be migrated to Jira in the near future. Because this BZ has already been cloned into Jira, I am closing it now to reduce the number of duplicate Jiras. This bug will be triaged for future work on the Jira issue that is shown in the Links section.