node

Any bare-metal or virtual machine on which you can install Automation Suite.

Kubernetes cluster

A set of nodes that host containerized applications.

provider

A service or API required by an application to function. It is a generalization of the ArgoCD application, as it may not necessarily result in an actual deployment, but only in a configuration to an external system. For example: an object store can be an internal Ceph application, or an external S3 bucket provided by MinIO.

dependency

A relationship between two ArgoCD applications, where one requires the other in order to function.

fabric stage

A step in the installation process where fabric applications are installed.

resource utilization

The resource consumption of a product during its usage.

resource request

The machine resources (CPU, memory) a product needs for an optimal installation and behavior. The associated resources are blocked for the entire product lifetime.

offline environment

A setup where the machines do not have access to the internet.

agent node

A machine hosting the worker pods (the functional services). You can design a machine to be used as both a server and agent. Having separate server and agent nodes in a deployment is a topology design decision.

server node

A bare-metal or virtual machine hosting the cluster management server.

application

Sometimes referred to as an ArgoCD-managed application, an application is an ArgoCD object that wraps around a Helm chart. It normally denotes a Helm chart deployment. ArgoCD manages the applications delivered in Automation Suite. Example: ceph, orchestrator, platform.

fabric

A collection of applications installed during the execution of the installer for the fabric stage. Examples: rancher-server, redis-cluster, fabric-installer.

services stage

A step in the installation process where service applications are installed.

ArgoCD

A declarative GitOps continuous delivery tool for Kubernetes. It is designed as a Kubernetes controller that continuously monitors UiPath running applications and checks the current state against the target state as specified in the docker registry.

UiPath product

Sometimes referred to as a product, a UiPath product is a collection of one or more applications that, together, provide a user-accessible service, for example, Orchestrator, Document Understanding, and others.

services

A collection of applications installed during the execution of the installer for the services stage. Examples: platform, orchestrator, sfcore, uipath, webhook.