Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Helm | 23,989 | 577 | 2 days ago | 289 | September 12, 2022 | 620 | apache-2.0 | Go | ||
The Kubernetes Package Manager | ||||||||||
Lens | 20,834 | 2 days ago | 885 | other | TypeScript | |||||
Lens - The way the world runs Kubernetes | ||||||||||
Charts | 15,483 | a year ago | 1 | apache-2.0 | Go | |||||
⚠️(OBSOLETE) Curated applications for Kubernetes | ||||||||||
Charts | 6,921 | a day ago | 163 | apache-2.0 | Mustache | |||||
Bitnami Helm Charts | ||||||||||
Helm Charts | 3,697 | 9 hours ago | 131 | apache-2.0 | Mustache | |||||
Prometheus community Helm charts | ||||||||||
Arkade | 3,384 | 2 | a day ago | 31 | April 24, 2021 | 76 | mit | Go | ||
Open Source Marketplace For Developer Tools | ||||||||||
Chartmuseum | 3,134 | 2 | 2 days ago | 42 | June 30, 2022 | 101 | apache-2.0 | Go | ||
Host your own Helm Chart Repository | ||||||||||
Awesome Apache Airflow | 3,060 | 7 months ago | 2 | Shell | ||||||
Curated list of resources about Apache Airflow | ||||||||||
Spark On K8s Operator | 2,293 | 21 | 3 days ago | 18 | April 24, 2021 | 454 | apache-2.0 | Go | ||
Kubernetes operator for managing the lifecycle of Apache Spark applications on Kubernetes. | ||||||||||
Kube Linter | 2,247 | 1 | 4 days ago | 14 | June 29, 2022 | 70 | apache-2.0 | Go | ||
KubeLinter is a static analysis tool that checks Kubernetes YAML files and Helm charts to ensure the applications represented in them adhere to best practices. |
Recursively generates Kubernetes manifests from a folder using Helm. This project began as a generator command for using with Flux.
Available at: Docker Hub and Quay.io.
Helm-generate renders Helm Charts recursively from a folder. It don't actually install any Chart, only render them, similar to helm template
. Helm repositories must be managed through helm cli, as helm-generate uses the same configuration as your helm binary.
How it works:
values.yaml
files.values.yaml
file.Helm-generate also handles the namespace injection on the manifests, as helm template
don't handle this this and we don't want to have a requirement for charts to have namespace defined.
There are two required keys on values.yaml
: namespace and releaseName. Those are internally used by helm-generate to correctly render the desired charts.
It is possible to inject (key -> value)
pairs to the top level of the values map through the CLI, using the flag --set my_key=my_value
. This flag is parsed as []string
, therefore it can be passed multiple times to inject multiple pairs. This flag overrides the values from values.yaml
.
This is a special control file designed to change the behavior of helm-generate for a specific folder, this don't apply to any subfolders. The current keys available at .helm.yaml are:
chart: repository/chart-name
chartVersion: 1.x.x
postRenderBinary: path-to-binary
If no .helm.yaml
is present at the same folder as a values.yaml
file, the default values are used.
Go module:
go get github.com/topfreegames/helm-generate
Build from source:
git clone github.com/topfreegames/helm-generate
cd helm-generate
make all
Usage:
helm-generate docs/examples/multiple-apps --default-chart=example-chart --default-chart-version=1.0.0