Domains

A domain is a logical Kubernetes deployment that groups related resources and defines a level of isolation between different environments. Domains help organize infrastructure and ensure that applications or processes run independently in each environment without interfering with one another.

Each domain acts like a separate space with resources separations. This allows teams to manage different chains without effects of each other.

Use Cases for Domains

One of the key advantages of using domains is their ability to isolate different chains from one another, ensuring that failures or issues in one domain do not propagate to others. For example, if a chain in one domain encounters an error, crashes, or consumes excessive resources, chains running in separate domains remain unaffected due to the logical separation enforced by the domain architecture. This allows you to assign a domain with more critical chains and allocate the necessary resources to it, while distributing less important chains across other domains. This isolation enhances system stability and resource management, making domains a critical tool for organizing workflows in complex environments.

User Interface Overview

Domains are accessible via the Admin Tools tab. Upon selecting Domains , the interface displays a structured list of all active domains, each defined by three critical attributes:

• Version: Indicates the domain’s configuration schema compatibility.
• Desired Engine: Specifies the execution engine version required for chains within this domain.
• Namespace: Reflects the underlying Kubernetes namespace enforcing resource isolation.

Domain Creation Workflow:
To deploy a new domain, administrators must provision it directly in Kubernetes (e.g., via kubectl or cluster management tools). This prerequisite ensures:

1. Strict alignment with infrastructure policies (resource quotas, network policies).
2. Automatic synchronization with QIP’s UI—once the Kubernetes namespace exists, it instantly appears in the domain list.
3. Enforcement of isolation guarantees at the infrastructure layer, preventing cross-domain resource conflicts.

Operational Insight:
The UI intentionally does not include an in-app "Add Domain" button. This design choice reinforces that domains are infrastructure-defined entities, not application-level configurations.