Fedora Account System
Red Hat Associate
Red Hat Customer
Why is this note to override cluster-wide default node selector in this section? Reported by: rhn-support-bkunal https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.3/html/deploying_openshift_container_storage/verifying-your-openshift-container-storage-installation_rhocs#annotations:def882d1-e5e9-41b6-8d92-4f6d7ac3a3ba
Hi bipin, Not sure when it was planned, but the reason for having the Note in 2 places is : 1. 1st Note Before Creation of Storagecluster(1.1.1. Installing Red Hat OpenShift Container Storage Operator using the Operator Hub) >> It was added so as to override cluster-wide default node selector before creation of Storage cluster. This step does not involve respinning CSI pods as they are not yet created 2. 2nd Note (2.1. Verify that the pods are in running state) >> This was added for users who want to override the cluster-wide default selector after Storage Cluster is already created. This step involves the extra step to respin CSI pods as well. IMO, we need some changes in the statement to clearly point out the reason for adding the notes in these 2 sections. Also, need to confirm from Annette if these commands are needed in OCS 4.5 and above ?
Hi Disha, I am OK with Bipin's suggestion to move the content from Verifying pods to some other section. But we would definitely need to keep both the content, or join them together, with a note : One is for pre-install of OCS and the 2nd one is for changing the selector after OCS is already installed.
Thank You so much Disha for including the change in all these docs listed in Comment#9 Verified that the following content is removed from Verifying the state of the pods -> Point #2. Moving to verified. NOTE When you need to override the cluster-wide default node selector for OpenShift Container Storage, you can perform the following steps through the command line interface: Specify a blank node selector for the openshift-storage namespace. $ oc annotate namespace openshift-storage openshift.io/node-selector= Delete the original pods generated by the DaemonSets. oc delete pod -l app=csi-cephfsplugin -n openshift-storage oc delete pod -l app=csi-rbdplugin -n openshift-storage Verified that the new content is added to the troubleshooting guide of all the versions (4.3, 4.4, 4.5). We need to decide if we need it in 4.6 as well. we will check and raise a new BZ if needed for the same ```````` When a cluster-wide default node selector is used for Openshift Container Storage, the pods generated by CSI daemonsets are able to start only on the nodes that match the selector. To be able to use Openshift Container Storage from nodes which do not match the selector, override the cluster-wide default node selector by performing the following steps in the command line interface : Procedure Specify a blank node selector for the openshift-storage namespace. $ oc annotate namespace openshift-storage openshift.io/node-selector= Delete the original pods generated by the DaemonSets. oc delete pod -l app=csi-cephfsplugin -n openshift-storage oc delete pod -l app=csi-rbdplugin -n openshift-storage ``````