Add Helm chart for Kubernetes deployment#7
Open
megative wants to merge 2 commits into
Open
Conversation
… and migration caveats in the Helm chart.
Member
|
Hello, have you tried to run on kubernetes? |
Contributor
Author
|
Hi, just locally on a kind cluster. The web has started however I'd like to make some additional tests since I've found problem with alerting in current realization just after creating of PR. Let's keep it as draft for a while because I need couple of days to return to it. I'll notify you additionaly. |
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
2 participants
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
Helm chart at
helm/incidentrelay: three deployments (web,scheduler,telegram) from the single image switched byINCIDENTRELAY_SERVICE, Service + optional Ingress,/healthz//readyzprobes with a startup probe covering entrypoint migrations, config rendered from values into a Secret (existingConfigSecretsupported), SQLite on a PVC or external PostgreSQL. Deployments default to theRecreateupdate strategy to protect the shared SQLite volume during rollouts. README gets a "Kubernetes (Helm)" install section.Known caveats are documented in values/NOTES/README: no public image is published yet (
image.repositorymust point at your own build), SQLite is single-node only, and migrations run on web pod start soweb.replicaCountshould stay at 1 unless migrations are moved out of band.Tests
No backend code is touched, so no tests are added: the change is deployment tooling only. Validated with
helm lint/helm templateacross value combinations and on a live kind cluster: all three workloads become Ready, probes pass, an alert sent through a real Alertmanager webhook receiver was ingested via a route intake token and acknowledged/resolved, and the SQLite database survives pod recreation on the PVC.