Bug 1991013 - Wrong CSI provisioner pods placement documentation
Summary: Wrong CSI provisioner pods placement documentation
Keywords:
Status: CLOSED DUPLICATE of bug 1960066
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Anjana Suparna Sriram
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-06 19:36 UTC by Pietro Bertera
Modified: 2023-08-09 16:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-09 07:16:01 UTC
Embargoed:


Attachments (Terms of Use)

Description Pietro Bertera 2021-08-06 19:36:17 UTC
Describe the issue: In OCS/ODF doc[1],[2] we mention that csi-provisioner pods should be scheduled on storage nodes

Table 2.1. Pods corresponding to OpenShift Container storage cluster, Section CSI:

~~~
* csi-cephfsplugin-provisioner-* (2 pods distributed across storage nodes)

[...]

* csi-rbdplugin-provisioner-* (2 pods distributed across storage nodes)
~~~

This is not accurate: the CSI provisioner pods can be placed on any worker node (storage or "pure" worker): the Deployment do not define any nodeSelector.

[1] https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.7/html/deploying_and_managing_openshift_container_storage_using_red_hat_openstack_platform/deploying-openshift-container-storage-on-red-hat-openstack-platform_internal-osp#verifying-the-state-of-the-pods_internal-osp
[2] https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.8/html/deploying_and_managing_openshift_container_storage_using_red_hat_openstack_platform/deploying-openshift-container-storage-on-red-hat-openstack-platform_internal-osp#verifying-the-state-of-the-pods_internal-osp

Comment 5 Pietro Bertera 2021-08-09 07:16:01 UTC

*** This bug has been marked as a duplicate of bug 1960066 ***


Note You need to log in before you can comment on or make changes to this bug.