For the complete documentation index, see llms.txt. This page is also available as Markdown.

☸️Standard Orchestrated container deployment

Standard Orchestrated container deployment (Kubernetes + Kots) for CARTO Self-Hosted

Standard Orchestrated container deployment

CARTO is deployed in an orchestrated environment on your existing Kubernetes cluster, using Kots to manage configuration and maintenance through the Admin Console UI.

How it works

CARTO services run as pods in your Kubernetes cluster and can be scaled horizontally. Kots installs into the cluster and exposes an Admin Console for configuration, versioned updates, and support bundles. The platform connects out to the external dependencies you provide: a PostgreSQL metadata database and object-storage buckets are always required, plus your data warehouse.

When to use it

This method might be appropriate if you and your team:

  • Already use Kubernetes to deploy other applications.

  • Have experience with Docker or DevOps concepts.

  • Require scalability, high availability, and resilience.

  • Prefer to use a UI for most configuration and maintenance tasks.

Characteristics

Aspect
Standard Orchestrated container deployment (Kots)

Infrastructure

An existing Kubernetes cluster

Configuration & maintenance

Kots Admin Console (web UI)

Scalability

Horizontal (multiple replicas)

High availability

Supported

Customization

Standard configuration options via the Admin Console

Best for

Production deployments on Kubernetes by teams who prefer a UI

What you'll need

Review the Prerequisites & Checklists, in particular the hardware & software requirements, the external metadata database, and object storage.

Next steps

Last updated

Was this helpful?