helm-release-plugin
Helm3 plugin that pulls(re-creates) helm Charts from deployed releases, and updates values of deployed releases without the chart. (by JovianX)
helm-secrets
A helm plugin that help manage secrets with Git workflow and store them anywhere (by jkroepke)
| helm-release-plugin | helm-secrets | |
|---|---|---|
| 2 | 12 | |
| 90 | 1,326 | |
| - | - | |
| 1.0 | 8.3 | |
| about 1 year ago | 6 days ago | |
| Shell | Shell | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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-release-plugin
Posts with mentions or reviews of helm-release-plugin.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Helm Release Time-To-Live(TTL)⏳💀 for Temporary Environments
Helm temporary releases are one of the most useful features in the Helm release plugin. A temporary release allows you to run an application, while you test a new feature or validate a fix, and then it gets deleted and purged after a certain period of time. Temporary releases can be deployed in a new Kubernetes namespace or in an existing one. The temporary application is effectively isolated from the rest of the Kubernetes cluster. It only has access to the resources that are allotted to it, and it iss are not affected by other pods, or the rest of the cluster. When you use a temporary environment to run the application, it is not impacting other apps running in the cluster. This means that they: Have their own set of persistent volumes, have their own set of APIs (endpoints, certificates, and so on). You’ll find that temporary environments are very useful for testing, staging, and debugging, since you can use them to run test pods without disturbing the rest of the Kubernetes cluster, and not worry about forgotten releases that keep consuming cloud resources, and keep spending your cloud budget.
- Helm plugin that recreates helm charts from deployed helm releases
helm-secrets
Posts with mentions or reviews of helm-secrets.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-09.
-
Simplified Deployment: A Deep Dive into Containerization and Helm
helm plugin install https://github.com/databus23/helm-diff helm plugin install https://github.com/aslafy-z/helm-git helm plugin install https://github.com/jkroepke/helm-secrets
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
I use Helm secrets which integrates Mozilla Sops to handle secrets in my Helm charts.
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 1/2
Use Helm Secrets.
-
Secret Management in Kubernetes: Approaches, Tools, and Best Practices
ArgoCD users would have to build container images with SOPS baked in using Helm chart extensions or Kustomize extensions. Flux allows configuring sops directly into the Flux manifests.
-
GitOps and Kubernetes – Secure Handling of Secrets
There is also the helm secrets plugin, which can also be used in ArgoCD with manual configuration.
-
Disable auto sync at application level when managed by ApplicationSet.
Not sure if this is applicable for your use case, but you could use helm-secrets to fetch remote value files from https or git: https://github.com/jkroepke/helm-secrets/wiki/Values
-
Goodbye Sealed Secrets, hello SOPS
$ helm plugin install https://github.com/jkroepke/helm-secrets --version v3.14.0
-
How should I manage my Helm charts?
https://github.com/jkroepke/helm-secrets powered by sops
-
Thoughts on using git-crypt
SOPS is great, and there are a lot of GitOps tools that either integrate with SOPS directly or make it relatively painless to integrate into your workflow, e.g. helm-secrets.
-
How to manage passwords in Helm
SOPS and helm-secrets: https://github.com/jkroepke/helm-secrets
What are some alternatives?
When comparing helm-release-plugin and helm-secrets you can also consider the following projects:
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
sops - Simple and flexible tool for managing secrets
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
argo-rollouts - Progressive Delivery for Kubernetes
hull - The incredible HULL - Helm Uniform Layer Library - is a Helm library chart to improve Helm chart based workflows
git-crypt - Transparent file encryption in git
fleet - Deploy workloads from Git to large fleets of Kubernetes clusters
kamus - An open source, git-ops, zero-trust secret encryption and decryption solution for Kubernetes applications
helm-s3 - ⎈ Helm plugin that adds support for AWS S3 as a chart repository.
KMSpico - Microsoft Windows & Office activation tools (copy from internet)
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
helm-secrets vs sealed-secrets
helm-secrets vs vault-secrets-operator
helm-secrets vs sops
helm-secrets vs argocd-operator
helm-secrets vs argo-rollouts
helm-secrets vs hull
helm-secrets vs git-crypt
helm-secrets vs fleet
helm-secrets vs kamus
helm-secrets vs helm-s3
helm-secrets vs KMSpico
helm-secrets vs awx