Instances¶

flowchart TD
    subgraph App["<div style='margin-top:10px; white-space: nowrap;'>App</div>"]
        subgraph group[ ]
            Dev["Dev instance"]
            Staging["Staging instance"]
            Prod["Production Instance"]
        end
        style group fill:none,stroke:none,stroke-width:0px          
    end

    KubernetesA["Kubernetes Cluster A"]
    KubernetesB["Kubernetes Cluster B"]

    Dev --> KubernetesB
    Staging --> KubernetesB
    Prod --> KubernetesA

An app instance is one isolated deployment of your application on a Kubernetes cluster.

Each instance has its own:

Environment, which is a named Env with a fixed type such as prod, staging, or dev
Stack revision
Endpoints to configure HTTP routes and published ports
Builds and deploys, when the stack has buildable services
Backups and imports, when the stack provides those capabilities
App services used to override stack configuration for this specific instance
Metrics, when cluster monitoring is enabled
live log streaming
Cron schedules and jobs
Tasks history

All instances of the same app share the same stack, but different instances can run on different clusters and different stack revisions.

App instances do not have a separate project owner. They belong to the app and use the app's ownership and sharing settings.

The instance machine name is permanent and must follow the general Kubernetes name rules. The generated namespace, <app-name>-<instance-name>, must be 63 characters or shorter.

You add or remove instances from Apps > [App] > Instances.

Instances¶

Related pages¶