- 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 in Kubernetes
- 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
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Velero backup fails with FailedValidation error
- External Secrets troubleshooting
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- TLS certificate validation errors
- Fluentd does not export logs in IPv6 environments
- Studio Desktop cannot load Integration Service connectors and activities
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Upgrade fails due to overridden Insights PVC sizes
Solutions for upgrade failures due to Insights PVC size overrides in Automation Suite on EKS/AKS.
Description
The upgrade can fail due to an issue where existing insights PVC sizes get overridden during the process. This issue occures due to unexpected changes to the PVC sizes that are not correctly reflected during the upgrade.
Solution
To address the problem, you must manually change the PVC sizes in ArgoCD UI:
-
In the ArgoCU UI, select Insights.
-
From the upper-left corner, select the Details button and then select the Parameters tab.
-
From the upper-right corner, select the Edit button and update the
sizeparameter underinsightslooker.insightslooker.persistenceaccording to your deployed PVC size.- To retrieve the correct size of
insights-looker-lookerdir-pvc, run the following command:kubectl get pvc -n uipath insights-looker-lookerdir-pvc -o json |jq -r .status.capacity.storagekubectl get pvc -n uipath insights-looker-lookerdir-pvc -o json |jq -r .status.capacity.storage - To retrieve the correct size of
insights-looker-datadir-pvc, run the following command:kubectl get pvc -n uipath insights-looker-datadir-pvc -o json |jq -r .status.capacity.storagekubectl get pvc -n uipath insights-looker-datadir-pvc -o json |jq -r .status.capacity.storage
- To retrieve the correct size of
-
After you update the VALUES field, select the SAVE button and sync Insights.