Skip to content

Document the Kubernetes/Helm installation - #36

Open
megative wants to merge 2 commits into
roxy-wi:release/2.0from
megative:docs/kubernetes-helm
Open

Document the Kubernetes/Helm installation#36
megative wants to merge 2 commits into
roxy-wi:release/2.0from
megative:docs/kubernetes-helm

Conversation

@megative

@megative megative commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Problem

The Helm chart in helm/incidentrelay has no documentation page. The only mention is a short section in the README, and docs/getting-started/ lists Docker, RPM and systemd as the available installation methods — Kubernetes is absent from the nav, from the installation dispatcher and from the getting-started table.

Change

New page getting-started/kubernetes.md:

  • what the chart deploys, and that every component runs the same image selected by INCIDENTRELAY_SERVICE
  • quick start, and how to pin an explicit image
  • how the config map is rendered into incidentrelay.conf, plus existingConfigSecret and the checksum/config caveat that comes with it
  • SQLite defaults and the single-node constraint; the PostgreSQL setup
  • migrations in the web entrypoint and what it takes to run more than one web replica
  • /healthz and /readyz semantics, ingress, first admin user, workers, custom voice providers
  • that helm uninstall removes the chart-created PVC along with the SQLite database

Linked from the installation dispatcher, the getting-started table, the mkdocs nav and the README.

Merge order

The page documents the Slack Socket Mode worker, which is added to the chart in #35. Merge #35 first — until then the slack section describes a component the chart does not ship, and slack.enabled is not a valid value.

Everything else on the page describes the chart as it is on release/2.0 today.

Notes

Rebased from main onto release/2.0 as requested. The Russian mirror that existed on main was dropped along the way, since docs/ru is not present on this branch.

Two rough edges operators will hit are described rather than worked around: the log volume is an emptyDir, and the application logs to files rather than stdout, so kubectl logs shows only the entrypoint banner.

No application or chart code is touched.

@Aidaho12

Copy link
Copy Markdown
Member

Hello, could you change branch to the release2.0. There is the changed

megative added 2 commits July 28, 2026 12:33
The chart in helm/incidentrelay had no documentation page: the only
mention was a short section in the README, and getting-started listed
Docker, RPM and systemd as the available methods.

Add getting-started/kubernetes.md covering what the chart deploys, how
values map onto incidentrelay.conf, the SQLite and PostgreSQL setups,
migrations and web scaling, probes, ingress, workers and uninstall
caveats. Mirror it into docs/ru and link it from the installation
dispatchers, the mkdocs nav and the README.
@megative
megative force-pushed the docs/kubernetes-helm branch from 1ce1315 to bace86a Compare July 28, 2026 10:34
@megative
megative changed the base branch from main to release/2.0 July 28, 2026 10:34
@megative

Copy link
Copy Markdown
Contributor Author

Rebased both PRs onto release/2.0 as requested.

Heads-up on translations: the English page is here, but I had to drop the Russian mirror. docs/ru does not exist on release/2.0 — it was added to main later in #30 (281e7a9), after this branch forked off Release/1.2 (#26), so all 90 translated pages live on main only. Adding a single docs/ru/getting-started/kubernetes.md here would resurrect a tree that isn't otherwise on the branch.

The RU text is preserved in this branch's history if it's useful later:

git show 1ce1315:docs/ru/getting-started/kubernetes.md

Is docs/ru meant to come over to release/2.0 at some point? If so, happy to add the Russian page in the same PR — just let me know.

@Aidaho12

Copy link
Copy Markdown
Member

I don't think so, to reduce conflict resolution. I'll translate the remaining documentation after the merge.

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.

2 participants