Skip to main content

GlueOps Captain Domains

GlueOps utilizes a deterministic DNS naming convention for your clusters and associated applications, providing a structured and organized way to access your deployed services.


The captain domain is automatically provided by GlueOps as part of its service.

Let's break down the components of a GlueOps captain domain using an example:

The domain consists of the following parts:

  1. Cluster Identifier (nonprod): This part represents the identifier of the cluster to which the application is deployed. In a typical setup, you might have both production and non-production (nonprod) clusters. For instance, a staging deployment of the order-api to a non-production cluster could look like Similarly, a production deployment of the same application to a production cluster would start with

  2. Tenant Key (antoniostacos): This component identifies your organization and remains common to all clusters deployed on the GlueOps platform.

  3. Core Domain for GlueOps Tenant Services ( This is the primary domain for the GlueOps tenant services.

The deterministic DNS naming convention ensures consistency and clarity in accessing your applications across different environments and clusters within the GlueOps platform. This organized approach simplifies application management and facilitates seamless communication between services.