When installing UiPath Automation Suite on Red Hat OpenShift, the deployment CLI toolchain (`uipathctl`) communicates with the OpenShift cluster via the Kubernetes API server endpoint. Consequently, the workstation or bastion host executing the installer does not require root or `sudo` administrative operating system privileges; the installer can be invoked by a standard user account on Linux, macOS, or Windows machines equipped with network access and valid OpenShift credentials. The deployment does, however, require Kubernetes-level privileges, including `cluster-admin` role bindings to register Custom Resource Definitions (CRDs), create target namespaces/projects, and manage workload constraints. UiPath microservices adhere to standard OpenShift security baselines, using the built-in `restricted-v2` Security Context Constraint (SCC) for workload execution. Eliminating the need for OS root access on bastion jump-hosts enforces the principle of least privilege in enterprise environments. (Reference: UiPath Automation Suite on Red Hat OpenShift – Installation Prerequisites and Access Permissions).
===============
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit