A lightweight Helm chart for Yopass that prioritizes transparency and flexibility.
Linted with kube-score,
kube-linter
and yamllint.
Tested with helm-unittest.
This chart may diverge from some common chart conventions. It favors transparency and flexibility over abstraction and convenience:
- Values-Driven: The goal is to provide a chart that can be understood just by looking at the values file. There should be no need to look into the templates to understand what the chart does and how it works.
- Minimal Abstraction: The chart avoids hidden logic and magic behavior as much as possible. A lot of what you see in the values file is what gets rendered in the templates.
- Flexibility over Convenience: The chart is designed to be flexible and understandable.
But this comes at the cost of convenience. Often you'll have to change multiple values to achieve the desired outcome.
For example, if you want to change the ports of the application,
you'd have to adapt the environment at
.Values.app.env, as well as.Values.containerPorts.
This chart does not bundle any databases (e.g., Postgres, Valkey) as a dependency. While this may seem inconvenient, it keeps the chart lightweight, and ensures users actively design their setup. Which database should be used? Is one already deployed? Should a new one be deployed? Is it deployed via helm chart or operator? Which helm chart should be used? Is a managed database service used? These are all questions that should be answered by the user, not the chart.
Please read the charts README.md to get started.
Please check the CONTRIBUTING.md to learn how to contribute.
You can install all required dependencies via Task and Homebrew
brew install go-task
task installIf you'd like to use other tools,
you can find all dependencies and relevant commands in the taskfile.yaml
task rendertask testtask linttask docs