High availability configuration for CARTO Self-hosted

For CARTO Self-hosted using Kots

This guide details configuring High Availability (HA) for CARTO Self-Hosted deployments using Kubernetes. HA ensures continuous service during server outages or failures, keeping your CARTO deployment operational.

Enabling high availability mode

To enable the high availability configuration on your CARTO Self-Hosted deployment, you'll have to check the following option in your configuration:

This change will enable the default options for high availability on your Self-Hosted installation, and we'll deploy multiple replicas for the services that are considered critical for CARTO platform's usage.

Customize your high availability options

In case you'd like to customize the high availability configuration, these are the available options:

Number of replicas for critical components:

• Minimum Number of Replicas: This setting determines the minimum number of copies of each CARTO service running at any given time. Increasing this value enhances fault tolerance by providing more replicas to handle requests during failures. The default value is 2.

• Maximum Number of Replicas: This setting defines the upper limit on the number of replicas for each service. This allows you to scale your deployment up or down based on usage. The default value is 3.

HTTP Cache resource allocation:

While the HTTP cache component doesn't support true HA, you can still optimize its performance by allocating resources:

• Cache Memory Request: This specifies the amount of RAM memory the cache container can request from your Kubernetes cluster.

• Cache CPU Request: This defines the amount of CPU units the cache container can request from your cluster.

By following these steps, you can configure a highly available CARTO deployment using Kubernetes. This setup ensures service continuity during failures, improving uptime and fault tolerance for your CARTO instance.