Documentation

Support

Unity Cloud

Get Started

Asset Manager SDKs and services

Open Unity Dashboard

Unity Cloud

Overview of the infrastructure

Learn about the infrastructure requirements for an on-premises deployment of Unity Virtual Private Cloud
Read time 1 minuteLast updated 9 hours ago

Infrastructure components

The deployment on premises runs entirely within your own Kubernetes cluster. The deployment creates and manages the following components inside the cluster:

Component

Description

Percona Server for MongoDB (PSMDB)Document database for asset metadata and application data
PostgreSQL (via PG Operator)Relational database for Keycloak and other services
RabbitMQMessage broker for asynchronous communication between services
ValkeyIn-memory data store for caching and session management
ElasticsearchSearch engine for asset indexing and discovery
RustFSObject storage for asset binary data and compatible with S3
TraefikIngress controller and load balancer
KeycloakIdentity and access management
Argo WorkflowsWorkflow engine for transformations and 3D streaming
Istio (optional)Service mesh for traffic management and observability
Loki and Alloy (optional)Log collection and aggregation
Percona Monitoring and Management (optional)Database monitoring
Prometheus (optional)Metrics collection

Infrastructure sizing

The deployment supports named sizing profiles that control CPU, memory, and storage allocations for infrastructure components. You configure the sizing profile in the manifest file: 
  • small
    : suitable for development and testing environments
  • medium
    (default): suitable for typical production workloads
  • large
    : suitable for high-traffic production environments
You can also override resource allocations for individual components. Read more about the configuration of the manifest in the deployment procedure.

Deployment waves

To satisfy dependencies, the deployment installs components in waves:
  1. Wave -3: cluster configuration, Istio base, and Prometheus stack
  2. Wave -2: operators and infrastructure services – Istio, Elasticsearch operator, database operators, Traefik, monitoring
  3. Wave -1: databases, caching, storage, and foundational services – Elasticsearch, PostgreSQL, MongoDB, RabbitMQ, Valkey, RustFS, UVCS, Keycloak, Argo Workflows
  4. Wave 0: application services – Asset Manager, automations, catalog, collaboration, and other microservices

Ingress

Traefik is deployed as the ingress controller. You configure the load balancer type and annotations in the manifest to match your environment, for example, an AWS Network Load Balancer (NLB) or a bare-metal load balancer.

Next steps

Prerequisites for the deployment