UiPath Platform: Architecture & Context [1/3]

Discover how Kubernetes outshines traditional infrastructure. We’ll cover cluster architecture, key components like pods, secrets, and deployments, dive into networking essentials, and explore how UiPath Automation Suite uses RKE2, Longhorn, Istio, Argo CD, and Registry—ending with a multi-node HAA 🎉


Agenda:





Kubernetes vs. Traditional Infrastructure. 



Overview of Kubernetes Cluster Architecture.
- What is a Master Node & its key components 
- What is a Worker Node & its key components 



Deepdive into Kubernetes components.
- Pods   
- Secrets and Config Maps   
- Deployments   



Kubernetes networking fundamentals.
Automation Suite Infra (RKE2, Longhorn, Istio, Argo CD, Registry)



Fabric & UiPath Service Components



Multinode HAA Architecture Walkthrough

Key Takeaways





Compare Kubernetes with traditional infrastructure.



Understand master/worker nodes and core components.



Learn networking basics and UiPath Infra tools.



See how multi-node high availability is achieved.

1. UiPath Automation Suite Community Workshop – Session 1/3 Date – 07 Oct 2025 The UiPath word mark, logos, and robots are registered trademarks owned by UiPath, Inc. and its affiliates. UiPath (R) is a registered trademark in the United States and several countries across the globe. See TMEP 906. ©2025 UiPath. All rights reserved.

2. Pawan Rathore Senior Technical Account Manager Ramkrishna Kadiya Technical Account Manager Welcome

3. UiPath Platform: Architecture & Context 07-Oct-2025 01

4. Agenda 01 02 03 04 Kubernetes vs. Traditional Infrastructure Overview of Kubernetes Cluster Architecture. Deep dive into Kubernetes components Automation Suite Infra 05 Kubernetes networking fundamentals 06 07 Fabric & UiPath Service Components Multi-node HAA Architecture Walkthrough 4

5. Feature Kubernetes Traditional Infrastructure Architecture Container-based orchestration Physical or Virtual Servers Scalability Horizontal scaling of containers Manual scaling (adding/removing servers or VMs) Infrastructure Provisioning Dynamic provisioning of resources based on demand Static provisioning (servers must be pre-configured) Fault Tolerance Built-in with container replication and failover Needs additional configuration or third-party tools Environment Consistency Uniform environment across Dev, Test, Prod Differences in environment between Dev, Test, Prod Portability High portability between different cloud providers or on-prem Tied to specific cloud or data center infrastructure 5 Kubernetes vs. Traditional Infrastructure

6. Overview of Kubernetes Cluster Architecture 6 Key components Master Node (Control Plane) Worker Nodes Networking Storage Pods: Smallest deployable units in Kubernetes, which run containers. Services: Define a logical set of pods and a policy to access them.

7. Component Purpose Function API Server (kube-apiserver) Exposes the Kubernetes API and acts as the central management interface for the cluster. Provides a REST interface to interact with the cluster. Validates and processes API requests. Serves as the entry point for all cluster communication, including from external clients and internal services. Scheduler ( kube -scheduler) Decides which node should run a particular pod based on resource availability and constraints. Watches for unscheduled pods and selects a node for them. Controller Manager (kube-controller-manager) Maintains the desired state of the cluster by managing controllers that ensure the current state matches the desired state. Runs controllers responsible for maintaining specific cluster states. Includes controllers like the ReplicaSet controller, Deployment controller, Node controller, etc. etcd A distributed key-value store used to store the cluster's state and configuration data. Stores all cluster data (e.g., configurations, metadata, and state) persistently. Serves as the source of truth for Kubernetes' desired state. Ensures consistency and coordination across the cluster. 7 Kubernetes Architecture – Master Node (Control Plane)

8. Component Purpose Function Kubelet Ensures containers are running in pods on the worker node. Kubelet is an agent that runs on each worker node, ensuring containers are running in the desired state. It communicates with the API Server to receive instructions on pod creation, termination, and monitoring. Kube-proxy Manages network traffic and load balancing within the node. Maintains network rules to allow communication between pods, services, and external networks. Performs load balancing for services running within the cluster. Container Runtime Runs the containers in the pods. Responsible for running containers on the worker node.- Supports multiple container runtimes such as Docker , containerd etc. 8 Kubernetes Architecture – Worker Node

9. A Pod is the smallest deployable unit in Kubernetes. It can host one or more containers that share the same network namespace, IP address, and storage. Pods are ephemeral and can be terminated or rescheduled by Kubernetes. 9 Deep dive into Kubernetes components Pods

10. Secrets are used to store and manage sensitive information. This helps keep sensitive data out of code or configuration files. Secrets are base64-encoded format. It's not encryption. It's important to secure access to the cluster to protect the actual data. By default, Secrets are stored in the cluster’s etcd database in plaintext. However, you can enable encryption to protect Secrets stored within etcd . Examples: API Key, API Secret, Database Username, Database Password etc. 10 Deep dive into Kubernetes components (Continued..) Secrets

11. ConfigMaps are used to store non-sensitive configuration data in key-value pairs and stored in etcd datastore. By using ConfigMaps , you can separate application configuration from application code, making it easier to update configurations without modifying or redeploying the application itself. ConfigMaps can store different types of configuration data, such as individual key-value pairs, entire configuration files, or even directories of configuration files. Examples: API Endpoint, Database Host, Database Port etc. 11 Deep dive into Kubernetes components (Continued..) ConfigMaps

12. Kubernetes Deployments manage the deployment and scaling of applications. Deployments allow you to declare the desired state of your application, and Kubernetes ensures that the actual state matches by automatically handling rollouts, scaling, and updates. Rolling Updates & Rollbacks Replica Management Self-Healing Version Control & History 12 Deep dive into Kubernetes components (Continued..) Deployments

13. Pod-to-Pod communication Pod-to-Service communication Service-to-Pod communication Service Types: ClusterIP NodePort LoadBalancer Ingress Network Policies 13 Kubernetes networking fundamentals Pod-to-Service communication

14. 14

15. 15

16. 16

17. RKE2 – Kubernetes Backbone of UiPath AS 🔹 Purpose in Automation Suite: • Provides the orchestration layer for all UiPath microservices (Orchestrator, AI Center, Apps, Insights, etc.). 🔹 Key Functions: • Service Orchestration – Deploys, scales, and self-heals UiPath services across nodes. • High Availability – Reschedules workloads automatically if a node fails. • Storage Integration – Works with Longhorn or Ceph for persistent volumes. • Security & RBAC – Enforces namespace isolation and access control. 🔹 Benefit to UiPath: • Provides a hardened, self-healing, cloud-native foundation for Automation Suite.

18. 18 🔹 Purpose in Automation Suite: • Acts as a service mesh managing inter-service communication within Kubernetes. • Provides ingress gateway for all incoming traffic to UiPath services. • Enforces mutual TLS ( mTLS ) between internal microservices. 🔹 Key Functions: • Traffic Management – Intelligent routing, retries, and timeouts. • Zero-Trust Policy – Only registered services can communicate. 🔹 Benefit to UiPath: • Simplifies security and routing across microservices. • Enables fine-grained control and encrypted internal traffic. Istio – Service Mesh & Secure Ingress

19. 19 🔹 Purpose in Automation Suite: • Manages declarative deployments of UiPath services in Kubernetes • Ensures cluster state matches version-controlled manifests. 🔹 Key Functions: • Automated Upgrades – Applies new UiPath releases automatically. • Rollback – Reverts to a stable version on failure. • Drift Detection – Detects and corrects manual config changes. 🔹 Benefit to UiPath: • Enables zero-downtime upgrades across all services. • Provides full traceability and auditability of configuration changes. Argo CD – Cluster Management

20. 20 🔹 Purpose in Automation Suite: • Hosts all UiPath service container images securely within the cluster. • Enables offline and air‑gapped deployments. 🔹 Key Functions: • Image Storage – Stores all UiPath service versions for deployment. • Version Control – Supports rollback and patch consistency. • Security – Optionally integrates with image vulnerability scanners. 🔹 Benefit to UiPath: • Ensures trusted image provenance with no external dependencies. • Provides faster upgrades and supports disconnected environments. Container Registry – Secure Image Distribution

21. 21 Session-2 (14-Oct-2025) Agenda UiPath Automation Suite Single Node installation Prerequisites - 24.10.x Hardware and software prerequisites. Deployment types & capacity planning. UiPath Automation Suite Single Node installation Prerequisite checks VM Disk Configuration. Setting up DNS. DB connectivity & Walkthrough of cluster config JSON. Installation of temp docker registry. Kubernetes Infra layer installation of server + agent. Initiate/Kick off - Service and fabric layer installation

22. Thank you