Skip to main content

​
Overview

PostGIS extends PostgreSQL with support for geographic objects and spatial queries, making it the standard choice for location-aware applications. This template deploys a single-replica PostGIS instance with persistent storage.
PostGIS on Control Plane operates as a single-replica deployment. Do not scale up the replica count, as this would result in multiple isolated instances rather than a replicated cluster.

​
What Gets Created

  • Stateful Workload — A single-replica PostGIS database container with configurable resources.
  • Volume Set — Persistent storage for database data, with optional autoscaling.
  • Secret — A dictionary secret storing the database username and password, injected into the container at startup.
  • Identity & Policy — An identity bound to the workload with reveal access to the database credentials secret.
This template does not create a GVC. You must deploy it into an existing GVC.

​
Installation

This template has no external prerequisites. To install, follow the instructions for your preferred method:

UI

Browse, install, and manage templates visually

CLI

Manage templates from your terminal

Terraform

Declare templates in your Terraform configurations

Pulumi

Declare templates in your Pulumi programs

​
Configuration

The default values.yaml for this template: 
image: postgis/postgis:17-3.5

resources:
  minCpu: 200m
  minMemory: 528Mi
  maxCpu: 500m
  maxMemory: 1024Mi

config:
  username: username
  password: password

postgres:
  database: database

volumeset:
  capacity: 10 # initial capacity in GiB (minimum is 10)
  autoscaling:
    enabled: false
    maxCapacity: 100 # Maximum capacity in GiB
    minFreePercentage: 10 # Trigger scaling when free space drops below this percentage
    scalingFactor: 1.2 # Multiply current capacity by this factor when scaling up

internalAccess:
  type: same-gvc # options: none, same-gvc, same-org, workload-list
  workloads: # Note: can only be used if type is same-gvc or workload-list
    #- //gvc/GVC_NAME/workload/WORKLOAD_NAME

​
Credentials

  • config.username — PostgreSQL username. Change before deploying to production.
  • config.password — PostgreSQL password. Change before deploying to production.
  • postgres.database — Name of the database created on startup.
These values are only applied on first startup when the data directory is empty. Updating them after the initial deployment will have no effect on the running database. To change credentials or the database name on an existing instance, use PostgreSQL’s native commands (e.g. ALTER USER, ALTER DATABASE).

​
Resources

  • resources.minCpu / resources.minMemory — Minimum CPU and memory guaranteed to the workload.
  • resources.maxCpu / resources.maxMemory — Maximum CPU and memory the workload can use.

​
Storage

  • volumeset.capacity — Initial volume size in GiB (minimum 10).
  • volumeset.autoscaling.enabled — Automatically expand the volume as it fills. When enabled:
    • maxCapacity — Maximum volume size in GiB.
    • minFreePercentage — Trigger a scale-up when free space drops below this percentage.
    • scalingFactor — Multiply the current capacity by this factor when scaling up.

​
Internal Access

  • internalAccess.type — Controls which workloads can connect to PostGIS on port 5432:
TypeDescription
noneNo internal access allowed
same-gvcAllow access from all workloads in the same GVC
same-orgAllow access from all workloads in the same organization
workload-listAllow access only from specific workloads listed in workloads

​
Connecting to PostGIS

Once deployed, connect to the database from within the same GVC using: 
RELEASE_NAME-postgis.GVC_NAME.cpln.local:5432

​
External References

PostGIS Documentation

Official PostGIS documentation

PostgreSQL Documentation

Official PostgreSQL documentation

PostGIS Template

View the source files, default values, and chart definition