Add Helm Chart for Pgwatch

[Joshna907]

Hey @pashagolub, I’m Jothsana Waikar.

I noticed that the current deployment focuses on Docker and Docker Compose, and I wanted to propose an idea to make it easier for Kubernetes users. I’d like to create a Helm chart for PGWatch.

The initial version of the chart would cover:

Deploying the PGWatch service using the existing Docker image

Configuring the metrics DB (Postgres) via Helm, with options for ports, persistence, and credentials

Deploying Grafana with the bundled dashboards

Basic customization via values.yaml (resources, ports, persistence, SSL, and admin credentials)

I’d love to hear your thoughts on this approach and whether there are any suggestions or best practices you’d recommend before I get started.

[pashagolub]

Check here before start https://github.com/cybertec-postgresql/pgwatch-charts

[Joshna907]

Hey @pashagolub — thanks for the pointer to the chart repo, I am so sorry I didn't knew it before, and yes I had a look through it. It already covers the core pieces (pgwatch, Postgres, Grafana, Prometheus), but I noticed the README flags the charts as “not production ready,” so there are a few safe, incremental improvements I could start with.

My suggested first small PRs would be:
Replace hardcoded credentials with Kubernetes Secrets and update templates to consume them.

Add sensible resource requests/limits in values.yaml and deployment templates.
After that I can move on to Grafana dashboard provisioning, more flexible persistence/ingress options, and integrating some of my init scripts as initContainers or hooks.

Would you prefer I start with Secrets or with resource limits? Also — are there any repo conventions (branch, linting, CI checks) or a preferred area you’d like prioritized? I can open an issue + a draft PR for the first item so you can review the direction before I proceed.

Thanks — I’m happy to follow whatever process you recommend.