☸️Standard Orchestrated container deployment

Get CARTO Self-Hosted running on Kubernetes with Kots in the shortest time possible

Standard Orchestrated container deployment

This quickstart walks you through the minimum steps to deploy CARTO Self-Hosted on a Kubernetes cluster using the Kots Admin Console. For a production-ready installation with full options and explanations, use the Standard Orchestrated container deployment guide.

Quickstarts are not suitable for production. For a production-grade installation with full configuration options, use the Deployment Guides.

Before you begin

Complete every item below before starting. Each prerequisite has a dedicated setup guide. Do not skip them.

• License file (license.yaml) received from CARTO Support → License / Customer Package

• Kubernetes cluster meets the hardware requirements for Standard Orchestrated deployments → Hardware & Software Requirements

• Metadata database (PostgreSQL 14+) provisioned and reachable from the cluster → Metadata Database prerequisites

• Object storage buckets created, CORS configured, and permissions set (Temp Bucket + Assets Bucket) → Object Storage prerequisites

• Network egress open for all required CARTO services → Network egress requirements

• kubectl installed and connected to your cluster

• A domain with DNS control and an SSL/TLS certificate ready

Steps

1. Install the Kots plugin for kubectl:

   curl https://kots.io/install | sudo bash

2. Install CARTO into your namespace and set an Admin Console password when prompted:

   kubectl kots install carto -n <namespace>

3. Open the Admin Console and log in, then upload your license:

   kubectl kots admin-console -n <namespace>
   # Go to http://localhost:8800

4. Configure required settings:

   • Metadata database — host, database, and credentials for your external PostgreSQL (plus its CA certificate for TLS).

   • Access to CARTO — your domain and SSL certificate. On GKE/EKS the default access mode provisions a load balancer from a cloud-managed certificate (enable the Gateway API on GKE).

   • Cloud Storage — your own buckets (see Configure your own buckets).

5. Run preflight checks and deploy. Review the checks on the dashboard, resolve any failures, then click Deploy.

6. Point DNS to the deployment's external IP. For the default access mode:

   # GKE
   kubectl get gateway -n <namespace> -o jsonpath="{.items[0].status.addresses[0].value}"

For optimal load balancer configuration and cloud provider recommendations, see Load balancing best practices.

Verify first success

Once deployment completes, confirm the following:

• All pods are running: kubectl get pods -n <namespace>

• The CARTO application loads at your configured domain over HTTPS

• You can log in with your admin credentials

• A basic map renders successfully

If any check fails, see Troubleshooting and Debug mode and logs.

Next steps

For a production-ready installation with full configuration options and post-install validation, follow the Standard Orchestrated container deployment guide.