PostgreSQL in containers - Docker, Kubernetes, production configs
Generates production-ready Docker and Kubernetes configurations for PostgreSQL containers. Claude will use this when you need to deploy PostgreSQL with proper resource limits, health checks, and persistent storage.
/plugin marketplace add pluginagentmarketplace/custom-plugin-postgresql/plugin install ultrathink@pluginagentmarketplace-postgresqlThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/config.yamlassets/docker-compose.yamlassets/schema.jsonreferences/GUIDE.mdreferences/PATTERNS.mdscripts/validate.pyAtomic skill for containerized PostgreSQL
Production-ready patterns for Docker and Kubernetes PostgreSQL deployments.
parameters:
platform:
type: string
required: true
enum: [docker, kubernetes, compose]
environment:
type: string
enum: [development, staging, production]
version: '3.8'
services:
postgres:
image: postgres:16-alpine
environment:
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
PGDATA: /var/lib/postgresql/data/pgdata
volumes:
- postgres_data:/var/lib/postgresql/data
ports:
- "5432:5432"
healthcheck:
test: ["CMD-SHELL", "pg_isready"]
interval: 10s
deploy:
resources:
limits:
memory: 4G
command:
- postgres
- -c
- shared_buffers=1GB
- -c
- max_connections=200
volumes:
postgres_data:
apiVersion: apps/v1
kind: StatefulSet
spec:
template:
spec:
containers:
- name: postgres
image: postgres:16
resources:
limits:
memory: "4Gi"
readinessProbe:
exec:
command: ["pg_isready"]
volumeMounts:
- name: data
mountPath: /var/lib/postgresql/data
# Pass config via command
postgres -c shared_buffers=1GB -c work_mem=64MB
# Use init scripts
./init.sql -> /docker-entrypoint-initdb.d/
| Workload | Memory | CPU |
|---|---|---|
| Dev | 512MB | 0.5 |
| Staging | 2GB | 1 |
| Production | 4GB+ | 2+ |
| Problem | Cause | Solution |
|---|---|---|
| OOM killed | Low memory limit | Increase limits |
| Slow startup | No init cache | Use pg_prewarm |
| Data loss | No volume | Mount persistent volume |
Skill("postgresql-docker")
Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.