automation-suite
2024.10
false
- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- 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 creation
- Troubleshooting
- Log streaming does not work in proxy setups
- 500 errors and rate limiting on S3 requests in ODF
- Configuring CSI driver tolerations for ODF 4.20
Automation Suite on OpenShift installation guide
Last updated Mar 26, 2026
Configuring CSI driver tolerations for ODF 4.20
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