helm-charts
charts
| helm-charts | charts | |
|---|---|---|
| 5 | 88 | |
| 66 | 8,414 | |
| - | 1.4% | |
| 5.4 | 10.0 | |
| 2 months ago | 7 days ago | |
| Smarty | Smarty | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
charts
-
Coexistence of containers and Helm charts - OCI based registries
Both of these examples seem pretty obvious and something you wouldn’t mess up, but as your chart grows, so does your values.yaml file. A great example is the Redis chart by Bitnami. I encourage you to scroll through its values file. See you in a minute!
-
How to deploy and manage a RabbitMQ cluster on Amazon EKS using Terraform and Helm
We will write a Terraform module that will take a list of configurations for each required RabbitMQ instance. Luckily for us, we don't have to write the Kubernetes yaml configurations since the helm charts by Bitnami does a great job of doing all the things we discussed above. All we need to do is leverage Terraform Helm Provider and deploy the chart with the required values for our use case.
-
Master Helm, Chart the Kubernetes Seas 🌊🧭🏴☠️
💡 The full details of helm charts can be referenced in their associated GitHub Repository.
-
Bitnami Kibana dashboard import
I have a configmap with the ndjson set up under data:, similar to https://github.com/bitnami/charts/issues/6159 and it's subsequent answer.
-
Deploy Kubernetes Helm Charts in Minutes
This way, you can easily deploy any Helm charts from this public repo - https://github.com/bitnami/charts/tree/main/bitnami in just minutes.
- [Kubernetes] Comment déployez-vous un cluster Postgres sur Kubernetes en 2022?
-
Is there any tutorial, blog post that shows you how to use the bitnami-mysql helm chart?
The Bitnami Github Pages themselves usually cover everything you need to know. Configure a values.yaml file, or modify that to your liking, and you run helm install, as written in their docs.
-
Dynamic Volume Provisioning in Kubernetes with AWS and Terraform
The actual reason that our pods are not coming up is found when we review the helm installation that we are trying to run. If you check the dependencies in the GitHub repository (https://github.com/bitnami/charts/blob/main/bitnami/drupal/values.yaml) you find out that persistent storage is enabled by default and set to 8Gi. Also, the helm package uses MariaDB and the database size is specified to a default of 8Gi, thus setting the minimum storage for this installation to be 16Gi.
-
Experience setting up Spark and Hudi on Kubernetes
We're using https://github.com/bitnami/charts/tree/main/bitnami/spark, but I have heard good things about https://github.com/GoogleCloudPlatform/spark-on-k8s-operator as well. Hudi should not need any long running deployments as per the docs https://hudi.apache.org/docs/0.5.1/deployment/#deploying
-
"helm crearte" command for bitnami charts/common Library?
Bitnami has its own scaffolding published at https://github.com/bitnami/charts/tree/main/template
What are some alternatives?
litmus-helm - Helm Charts for the Litmus Chaos Operator & CRDs
helm-charts - A curated set of Helm charts brought to you by codecentric
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.
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
kluctl - The missing glue to put together large Kubernetes deployments, composed of multiple smaller parts (Helm/Kustomize/...) in a manageable and unified way.
renovate - Universal dependency automation tool.
helm-charts - A collection of Helm charts
promscale - [DEPRECATED] Promscale is a unified metric and trace observability backend for Prometheus, Jaeger and OpenTelemetry built on PostgreSQL and TimescaleDB.
ark-server-charts - A helm chart for an ARK Survival Evolved Cluster
kube-thanos - Kubernetes specific configuration for deploying Thanos.
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
kubegres - Kubegres is a Kubernetes operator allowing to deploy one or many clusters of PostgreSql instances and manage databases replication, failover and backup.