- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- 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
- Troubleshooting
Automation Suite on OpenShift installation guide
This step is required only if you want to store sensitive credentials in an external secret-management system.
By default, Automation Suite includes the External Secrets Operator.
If you choose not to use the bundled version, you can install your own External Secrets Operator instance by following the steps described in this section.
The External Secrets Operator (ESO) is a Kubernetes operator that integrates external secret-management systems. It reads data from external APIs and automatically injects the values into Kubernetes Secrets.
Automation Suite currently supports Azure Key Vault, and we are working on bringing support for additional secret managers in future releases.
To install the External Secrets Operator on OpenShift, follow the instructions in the official Red Hat documentation.
