helm-charts
nfs-provisioner
helm-charts | nfs-provisioner | |
---|---|---|
5 | 2 | |
66 | 2 | |
- | - | |
5.4 | 7.7 | |
2 months ago | almost 2 years ago | |
Smarty | Smarty | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
helm-charts
-
Podman Desktop 1.6 released: Even more Kubernetes and Containers features
There's a number or solutions. One is to use a maintained Helm Library Chart that exposes all the values most could ever want like The Helmet [1]. The other is to move over to something like Timoni that is analogous to Helm but with better templating [2].
[1] https://github.com/companyinfo/helm-charts/tree/main/charts/...
[2] https://timoni.sh/comparison/
-
"helm crearte" command for bitnami charts/common Library?
Try Helmet
-
Alternatives to Helm?
My alternative to Helm is more effective use of Helm. I learned about the Helmet library chart a few weeks ago: https://github.com/companyinfo/helm-charts/tree/main/charts/helmet
- Kubernetes: converting terraform deployments and resources to something better, like helm?
-
The Helmet is a Helm Library Chart that defines many chart templates like Deployment, Service, Ingress, etc which can used in other application charts.
The Helmet library was created because we saw many charts requiring only a few select configuration options in their Helm charts.
nfs-provisioner
-
How do volumes behave if the accessing pods are moved to a different node?
Pretty sure that if you are using local storage provisioner, the volume won't move with the pod to another node. To have storage accessible from all nodes you can use, e.g., an nfs provisioner on that node with nvme. I run this on bare metal at least and it works fine.
-
K3S Setup Advice
Persistent storage has some options, but if you have a NAS, you can create a storage class and a provisioner similar to this one. This helm chart also includes an nfs server sharing storage from one of the nodes, you might not need that.
What are some alternatives?
litmus-helm - Helm Charts for the Litmus Chaos Operator & CRDs
k3s-ansible
charts - The User-Community Airflow Helm Chart is the standard way to deploy Apache Airflow on Kubernetes with Helm. Originally created in 2017, it has since helped thousands of companies create production-ready deployments of Airflow on Kubernetes.
helm - Helm chart for authentik
kluctl - The missing glue to put together large Kubernetes deployments, composed of multiple smaller parts (Helm/Kustomize/...) in a manageable and unified way.
falcon-helm - Helm Charts for running CrowdStrike Falcon with Kubernetes
helm-charts - A collection of Helm charts
apisix-helm-chart - Apache APISIX Helm Chart
ark-server-charts - A helm chart for an ARK Survival Evolved Cluster
k3s - Lightweight Kubernetes
clearml-helm-charts - Helm chart repository for the new unified way to deploy ClearML on Kubernetes. ClearML - Auto-Magical CI/CD to streamline your AI workload. Experiment Management, Data Management, Pipeline, Orchestration, Scheduling & Serving in one MLOps/LLMOps solution
k3sup - bootstrap K3s over SSH in < 60s 🚀