When consolidating multiple, isolated Automation Suite environments (e.g., Development, Staging, or multiple business units) within a shared Red Hat OpenShift cluster, tenant isolation and state boundary integrity are enforced at the namespace level. UiPath microservices depend on Redis for distributed caching, user session state storage, and transient queuing across services like Orchestrator and Identity Server. In a multi-instance scenario on a single cluster, engineers must install an independent Redis instance within each corresponding Automation Suite namespace and subsequently update the respective `input.json` deployment file with the distinct Redis host connection strings. Sharing a single, centralized Redis deployment across multiple distinct Automation Suite namespaces is unsupported because cache key collisions, session cross-talk, and unified cache flushes would compromise tenant data separation and operational availability. Namespace-isolated Redis deployments maintain predictable caching latencies and adhere to OpenShift security context constraints. (Reference: UiPath Automation Suite on OpenShift – Multi-Tenancy and Shared Cluster Topologies).
===============
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