Outboxx is built to run under a supervisor: fail-fast process, /healthz and /readyz for probes, /metrics for Prometheus. Kubernetes is the natural supervisor, but the repo has no deployment story beyond the GHCR image: no chart, no manifests, no docs.
Ask:
- Helm chart: Deployment with a single replica and the
Recreate strategy (the replication slot allows one consumer), env from a Secret for the libpq conninfo and the Kafka SASL password, liveness/readiness probes wired to /healthz and /readyz, optional ServiceMonitor.
- Publish the chart as an OCI package to GHCR from the release workflow.
- A "Running on Kubernetes" section in the docs, plus plain manifests for non-Helm users.
Outboxx is built to run under a supervisor: fail-fast process,
/healthzand/readyzfor probes,/metricsfor Prometheus. Kubernetes is the natural supervisor, but the repo has no deployment story beyond the GHCR image: no chart, no manifests, no docs.Ask:
Recreatestrategy (the replication slot allows one consumer), env from a Secret for the libpq conninfo and the Kafka SASL password, liveness/readiness probes wired to/healthzand/readyz, optional ServiceMonitor.