feat(helm): add official Helm chart for Kubernetes deployment (#49) - #2031
Open
sloemo01 wants to merge 1 commit into
Open
feat(helm): add official Helm chart for Kubernetes deployment (#49)#2031sloemo01 wants to merge 1 commit into
sloemo01 wants to merge 1 commit into
Conversation
…se-dev#49) SQLite + PVC by default (matching the project's store), PostgreSQL opt-in via values. API keys mount from a Secret (generated or existing), probes hit the unauthenticated /health endpoint, and the chart builds on the existing docker/Dockerfile image — no new image. Repos mount read-only at /repos/<name>, mirroring docker-compose. Replicas pinned to 1: the SQLite file and vector store live on the PVC, so a second replica would race on the same volume. Verified: helm lint clean, helm template renders Deployment/Service/PVC/ Secret/Ingress/ServiceAccount for both the SQLite and PostgreSQL paths.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fixes #49. Official Helm chart for Kubernetes deployment, per the constraints in the thread.
Root cause
No first-class Kubernetes deployment path existed — docker-compose was the only orchestration story, and it doesn't cover PVC lifecycle, Secret management, or probes.
Changes
postgresql.enabled(switchesREPOWISE_DB_URLto a DSN, suppresses the SQLite PVC)./health— the unauthenticated liveness/readiness endpoint.docker/Dockerfileimage — no new image; same env vars and volume mounts as docker-compose, mapped to k8s resources./repos/<name>(hostPath or PVC), mirroring docker-compose.Structure:
charts/repowise/— Chart.yaml, values.yaml, templates (Deployment, Service, PVC, Secret, Ingress, ServiceAccount, NOTES), README with config reference.Tests
helm lintclean;helm templaterenders correctly for both the SQLite default and PostgreSQL opt-in paths, and with ingress enabled.Note:
test_plugin_contentis red on main itself (v0.47.0 release bug, unrelated to this PR).