Run PostgreSQL as a database for Kubernetes applications managed by Wodby.
This repository defines the Wodby service manifests and operational configuration for PostgreSQL.
- Chatwoot application stack
- Dagster application stack
- Django application stack
- Drupal application stack
- FastAPI application stack
- Flask application stack
- Go application stack
- Next.js application stack
- Node.js application stack
- PHP application stack
- PostgreSQL application stack
- Python application stack
- Rails application stack
- Ruby application stack
| Property | Manifest configuration |
|---|---|
| Service name | postgres |
| Type | Database |
| Versions | 18 by default |
| Workloads | main (StatefulSet), primary; fixed replica count |
| Containers | postgresql using wodby/postgres |
| Endpoints | postgres: TCP 5432 |
| Volumes | Data, 10 GB |
| Helm | chart oci://registry-1.docker.io/wodby/postgres; version 0.3.2 |
| Configuration | 1 configuration files, 3 generated or fixed tokens |
| Operations | 1 import workflows, 1 backup workflows |
Use this service through one of the Wodby application stacks listed above, or
reference postgres from a custom Wodby stack.
A service is a reusable component and does not deploy by itself. The stack defines its links, settings, versions, resources, and relationship to the rest of the application.
The PostgreSQL 18 image includes pgvector, but the service does not enable any
database extension by default. Stacks that require pgvector can add vector to
POSTGRES_DB_EXTENSIONS; the configured extensions are created in both the
initial database and databases provisioned through Wodby.
- Fork this repository.
- Edit the service manifest and referenced files.
- Import the repository as a Git-backed service.
- Reference the service from a stack manifest.
Keep service, workload, container, endpoint, link, volume, config, and derivative names stable unless dependent stacks and app-level overrides are updated at the same time.
Validate the manifests with:
wodby service validate-manifest service.yml --org <org-id>See the service manifest reference and the managed services index.