automation-suite
2.2510
true
Automation Suite on OpenShift installation guide
- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions with cluster roles
- Granting installation permissions without cluster roles
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library installation
- AI Trust Layer
- Troubleshooting
- 500 errors and rate limiting on S3 requests in ODF
- External Secrets troubleshooting
- Configuring CSI driver tolerations for ODF 4.20
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- Studio Desktop cannot load Integration Service connectors and activities
- TLS certificate validation errors
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Configuring CSI driver tolerations for ODF 4.20
Configure Ceph CSI driver tolerations for OpenShift Data Foundation 4.20 in Automation Suite.
Description
OpenShift Data Foundation (ODF) 4.20 uses rook 1.18, which factors out Ceph CSI drivers into a separate operator. As a result, the previous method of passing tolerations through the CSI_PLUGIN_TOLERATIONS configmap no longer works. To ensure that Ceph CSI nodeplugins are scheduled on the correct nodes, you must explicitly add tolerations to the Ceph CSI nodeplugins.
Solution
After the storagecluster has been successfully deployed, take the following steps:
- Save the following configuration to a YAML file:
--- apiVersion: csi.ceph.io/v1 kind: Driver metadata: name: openshift-storage.cephfs.csi.ceph.com namespace: openshift-storage spec: nodePlugin: tolerations: - effect: NoSchedule key: node.ocs.openshift.io/storage operator: Equal value: "true" - effect: NoSchedule key: serverless.robot operator: Equal value: "present" - effect: NoSchedule key: node-role.kubernetes.io/control-plane operator: Exists - effect: NoSchedule key: uipath operator: Exists --- apiVersion: csi.ceph.io/v1 kind: Driver metadata: name: openshift-storage.rbd.csi.ceph.com namespace: openshift-storage spec: nodePlugin: tolerations: - effect: NoSchedule key: node.ocs.openshift.io/storage operator: Equal value: "true" - effect: NoSchedule key: serverless.robot operator: Equal value: "present" - effect: NoSchedule key: node-role.kubernetes.io/control-plane operator: Exists - effect: NoSchedule key: uipath operator: Exists--- apiVersion: csi.ceph.io/v1 kind: Driver metadata: name: openshift-storage.cephfs.csi.ceph.com namespace: openshift-storage spec: nodePlugin: tolerations: - effect: NoSchedule key: node.ocs.openshift.io/storage operator: Equal value: "true" - effect: NoSchedule key: serverless.robot operator: Equal value: "present" - effect: NoSchedule key: node-role.kubernetes.io/control-plane operator: Exists - effect: NoSchedule key: uipath operator: Exists --- apiVersion: csi.ceph.io/v1 kind: Driver metadata: name: openshift-storage.rbd.csi.ceph.com namespace: openshift-storage spec: nodePlugin: tolerations: - effect: NoSchedule key: node.ocs.openshift.io/storage operator: Equal value: "true" - effect: NoSchedule key: serverless.robot operator: Equal value: "present" - effect: NoSchedule key: node-role.kubernetes.io/control-plane operator: Exists - effect: NoSchedule key: uipath operator: Exists - Apply the configuration by running the following command:
oc apply -f <filename>.yamloc apply -f <filename>.yaml