Create and prepare the necessary namespaces in Red Hat OpenShift
ObjectScale and certain CSI components require their own namespaces (an OpenShift project) to properly function. You can create namespaces for each object store.
Prerequisites
If the ObjectScale Qualification Tool precheck report showed another scheduler extender on the cluster, follow the OpenShift steps of
Manual Kubernetes Scheduler Configuration from
https://github.com/dell/csi-baremetal-operator/blob/master/docs/MANUAL_SCHEDULER_CONFIGURATION.md. These steps ensure that the current scheduler extender is NOT overwritten. Do these steps before you deploy the Bare-Metal CSI Driver.
About this task
Complete these steps to create and prepare the required namespaces.
Create a namespace where you can install the secondary scheduler operator.
Red Hat provides this secondary scheduler operator, which is Kubernetes-level software like the default scheduler. You must install the secondary scheduler on its own namespace.
kubectl create ns $SSO_NS
Create a namespace where you can install the CSI Bare-Metal components.
kubectl create ns $CSI_NS
Create a namespace where you can install ObjectScale.
kubectl create ns $OBJECTSCALE_NS
Optional: Create a namespace for one or more object stores.
You can deploy object stores within the same namespaces as ObjectScale or within their own, separate namespaces.
kubectl create ns <OBJECT_STORE_NAMESPACE>
Add privileges for pod security for the namespaces.
Apply the privileges for pod security to the secondary-scheduler operator namespace.
Where:
<CSI_NAMESPACE> is the name of your CSI namespace.
Apply these
yaml files.
Apply the
role.yaml.
kubectl apply -f role.yaml -n $CSI_NS
Apply the
rolebinding.yaml.
kubectl apply -f rolebinding.yaml -n $CSI_NS
You should ensure that the OCP cluster global registry pull secret includes the registry pull secret for the docker.io registry server. If the registry pull secret for docker.io is already in the global cluster pull secret, you may skip the steps below. If the registry pull secret must be added or updated, follow the steps below.
Download the current OCP global pull secrets to a temporary file.
Enter the following command to add or update the registry secret for the registry server which hosts the ObjectScale images to the temporary file.
oc registry login --registry="docker.io/objectscale" --auth-basic="<username>:<password>" --to=ocp_cluster_pull_secret
<username>:<password> - registry user name and password
Enter the following command to update the global registry pull secret.
oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=ocp_cluster_pull_secret
Delete the temporary file.
rm -f ocp_cluster_pull_secret
The update to registry pull secret is rolled out to all nodes in the cluster. This update can take some time, depending on the size of the cluster.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\