- 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
How to deploy Insights in a FIPS-enabled cluster
Deploy Insights on dedicated non-FIPS node in FIPS-enabled OpenShift cluster.
Insights does not currently support FIPS. However, you can deploy Insights in a FIPS-enabled cluster by running it on a dedicated non-FIPS node using node selectors and tolerations.
Take the following steps:
-
Add a non-FIPS node to your FIPS-enabled cluster.
-
Apply a taint to the non-FIPS node to prevent other workloads from scheduling on it, and assign it a label that matches the node selector you will configure in the next step.
-
In the
input.jsonfile, configure Insights to run exclusively on the non-FIPS node using node selectors and tolerations:{ "insights": { "enabled": true, "advanced_configuration": { "global": { "nodeSelectorLabels": { "nodename": "insights" }, "tolerations": [ { "key": "insights", "operator": "Equal", "value": "true", "effect": "NoSchedule" } ] } } } }{ "insights": { "enabled": true, "advanced_configuration": { "global": { "nodeSelectorLabels": { "nodename": "insights" }, "tolerations": [ { "key": "insights", "operator": "Equal", "value": "true", "effect": "NoSchedule" } ] } } } }Note:Make sure the
nodeSelectorLabelsandtolerationsmatch the labels and taints you applied to your non-FIPS node. -
Apply the configuration by rerunning the Automation Suite installer.