Skip to content

Add Kubernetes deployment manifests #47

Closed

Description

@jsam

Problem

Only an Ingress example exists in docs. No Deployment, Service, StatefulSet, or PersistentVolumeClaim manifests are provided. Users deploying to K8s must write all manifests from scratch.

Action

  • Add deploy/kubernetes/ directory with:
    • statefulset.yaml (persistent storage needs StatefulSet, not Deployment)
    • service.yaml
    • pvc.yaml
    • ingress.yaml (already have example)
    • configmap.yaml for config.toml
  • Consider a Helm chart for parameterized deployments
  • Add deployment documentation

Generated from production readiness audit

Activity

  1. self-assigned this
    on Mar 17, 2026
  2. added
    enhancementNew feature or request
    infraInfrastructure, CI/CD, DevOps
    on Mar 17, 2026
  3. jsam commented on Oct 1, 2026

    @jsam
    ContributorAuthor

    The docs have inline manifests, but the Deployment with an RWO PVC can run two servers on one data dir, and there is no fsGroup. Switch to a StatefulSet with securityContext, add a ConfigMap, mirror it to deploy/kubernetes/ and validate with kubeconform. Helm is optional. The data-dir exclusive lock is filed separately.

  4. added this to the Ops & resources milestone on Oct 3, 2026
  5. added
    backendBackend/server related
    P1Required next for reliable reactive delivery and operations
    on Oct 3, 2026
  6. added 3 commits that reference this issue on Oct 3, 2026
    9dc2922
    57a2ce3
    2feef73
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1Required next for reliable reactive delivery and operationsbackendBackend/server relatedenhancementNew feature or requestinfraInfrastructure, CI/CD, DevOps

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions