Skip to content

feat(helm): Add self-hosting Helm chart for Svix webhook service #1967

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

adityawdubey
Copy link

Motivation

Svix does not provide an official or supported Helm chart for self-hosting. Users looking to deploy Svix on Kubernetes must manually provision the backend, database, Redis, and other components, often leading to fragmented, error-prone, or insecure setups.

This makes it harder for DevOps teams to adopt Svix in environments where Kubernetes and Helm are standard deployment tools. Without a reusable Helm chart, managing upgrades, scaling, or secure configuration becomes more difficult and inconsistent across teams.

Solution

This PR introduces a fully functional Helm chart to deploy the entire Svix webhook stack on Kubernetes. It includes:

  • Templates for the Svix backend, PostgreSQL, PgBouncer, and Redis
  • Support for external database endpoints
  • Configurable values for secrets and resourcesBuilt-in health checks
  • Built-in health checks, service definitions, and PVC support
  • Horizontal Pod Autoscaler (HPA) for svix-backend based on CPU and memory utilization, enabling automatic scaling under load
  • A comprehensive README.md with deployment guidance and production best practices
  • Added .gitignore for Helm chart to exclude rendered files and secrets

This addition allows users to self-host Svix reliably, reproducibly, and securely using Helm — supporting both local testing and production deployments out of the box.

@adityawdubey adityawdubey marked this pull request as ready for review July 25, 2025 19:15
@adityawdubey adityawdubey requested a review from a team as a code owner July 25, 2025 19:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant