Chapter 3. Verifying OpenShift Container Storage deployment for internal mode

Procedure

1. Click Workloads Pods from the left pane of the OpenShift Web Console.

2. Select openshift-storage from the Project drop down list.

   For more information on the expected number of pods for each component and how it varies depending on the number of nodes, see Table 3.1, “Pods corresponding to OpenShift Container storage cluster”.

3. Verify that the following pods are in running and completed state by clicking on the Running and the Completed tabs:

   Expand

   Table 3.1. Pods corresponding to OpenShift Container storage cluster

   Component	Corresponding pods
   OpenShift Container Storage Operator	ocs-operator-* (1 pod on any worker node) ocs-metrics-exporter-*
   Rook-ceph Operator	rook-ceph-operator-*
   Multicloud Object Gateway	noobaa-operator-* noobaa-core-* noobaa-db-pg-* noobaa-endpoint-*
   (1 pod on any worker node) (1 pod on any storage node) (1 pod on any storage node) (1 pod on any storage node) (3 pods distributed across storage nodes) (For arbiter, 5 pods are distributed across 3 zones, 2 per data-center zones and 1 in arbiter zone)	MGR
   rook-ceph-mgr-* (1 pod on any storage node)	MDS
   rook-ceph-mds-ocs-storagecluster-cephfilesystem-* (2 pods distributed across storage nodes)	CSI
   cephfs csi-cephfsplugin-* csi-cephfsplugin-provisioner-* rbd csi-rbdplugin-* csi-rbdplugin-provisioner-*	(1 pod on each worker node) (2 pods distributed across storage nodes) (1 pod on each worker node) (2 pods distributed across storage nodes)
   rook-ceph-crashcollector	rook-ceph-crashcollector-* (1 pod on each storage node) (For arbiter, 1 pod on each storage node and 1 pod in arbiter zone)
   OSD	rook-ceph-osd-* (1 pod for each device) rook-ceph-osd-prepare-ocs-deviceset-* (1 pod for each device)

   Show more