- 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
- Accessing Automation Suite
- Managing the certificates
- Managing the cluster in ArgoCD
- Managing products
- Updating credentials
- Migration and upgrade
- Cluster administration
- Product-specific configuration
- Troubleshooting
Accessing Automation Suite
Before running any oc commands, make sure you have downloaded and installed oc on your client machine. This allows you to run commands for retrieving passwords and configuration details for the cluster.
The installation process generates self-signed certificates on your behalf. You should replace them with certificates signed by a trusted Certificate Authority (CA) as soon as installation completes.
For instructions, see Managing certificates.
If you try to access the cluster with a web browser, and the certificates are not from a trusted CA, then you will see a warning in the browser. You can rectify this by importing and trusting the cluster SSL certificate on the client computer running the browser.
To manage certificates, take the following steps:
The general-use Automation Suite user interface serves as a portal for both organization administrators and organization users. It is a common organization-level resource from where everyone can access all of your Automation Suite areas: administration pages, platform-level pages, product-specific pages, and user-specific pages.
To access Automation Suite, take the following steps:
The host portal is for system administrators to configure the Automation Suite instance. The settings that you configure from this portal are inherited by all your organizations, and some can be overwritten at the organization level.
To access host administration, take the following steps:
You can access the database connection strings for each service as follows:
oc -n <uipath> get secret aicenter-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret orchestrator-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret automation-hub-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret automation-ops-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret insights-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret platform-service-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret test-manager-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret aicenter-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret orchestrator-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret automation-hub-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret automation-ops-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret insights-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret platform-service-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
oc -n <uipath> get secret test-manager-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode