Skip to content
MagmaMoosePublic

About

Helm

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

47 Commits

Folders and files

Repository files navigation

charts

Helm charts for MagmaMoose infrastructure, published as OCI artifacts to ghcr.io/magmamoose/charts.

There is no chart repository to add, no index.yaml, and no gh-pages branch:

helm install kafka-tester oci://ghcr.io/magmamoose/charts/kafka-tester --version 0.1.1

Flux points at the same place with a type: oci HelmRepository.

Charts

Chart
kafka-tester kafka-tester: test any Kafka endpoint's health from a small web UI

Conventions

Chart version and appVersion move independently. The chart version tracks this repository and is set at release time by GitVersion. appVersion names the application image tag and is bumped in Chart.yaml when that image is upgraded. Charts here use appVersion as the default image tag, so the two must not be forced equal.

Guards over documentation. Configuration mistakes that would be slow to diagnose in a live cluster — custom endpoints off with no targets, two targets with one name — fail helm template with the reason instead. See templates/_guards.tpl in a chart, and the CI job that asserts each guard still fires.

values.schema.json for shape, guards for context. JSON Schema validates types and enums; it cannot express "this is only wrong given that other value", and its errors are poor. Cross-field rules live in the guards.

Comments explain why, not what. A comment that restates the YAML beneath it is noise; one that records the failure a line prevents is the reason the line survives the next refactor.

Releasing

Push to main with a conventional-commit message. Diatreme computes the next repository version, tags it and publishes the GitHub Release. Charts are versioned on their own: the publish workflow pushes each chart at the version in its Chart.yaml and skips versions that are already published. So a change to a chart ships only if it also bumps that chart's version. CI fails a pull request that changes a chart without bumping it.

Contributing

ct lint plus a render-and-validate pass against the real Kubernetes API schemas runs on every pull request. To reproduce locally:

helm lint charts/kafka-tester --values charts/kafka-tester/ci/default-values.yaml
helm template t charts/kafka-tester --values charts/kafka-tester/ci/default-values.yaml | kubeconform -strict -summary

About

Helm

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages