configurator
vault-secrets-operator
| configurator | vault-secrets-operator | |
|---|---|---|
| 1 | 5 | |
| 112 | 611 | |
| - | - | |
| 4.2 | 8.0 | |
| 3 months ago | 5 days ago | |
| Go | Go | |
| GNU General Public License v3.0 or later | MIT License |
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.
configurator
-
Using Helm Charts with Configurator - A versioning & sync service for Kubernetes ConfigMaps
You can take a look at this open-source project @ https://github.com/gopaddle-io/configurator.git.
vault-secrets-operator
- Toyota Accidently Exposed A Secret Key Publicly On GitHub For Five Years
-
Learning with K3s at home. Is it "better" to store secrets encrypted in the git repo (e.g., sealed-secrets) or in a separately managed secret database (e.g., vault)?
For home use, I wouldn't bother with Vault unless that's really what you want to learn. Then it's worth looking into setting something up where you could use vault secrets, using one of the available options (I haven't seen the vault-secrets-operator being mentioned).
-
Hashicorp Vault integration with Secret objects
It is but it affects vault-secrets-operator too, see https://github.com/ricoberger/vault-secrets-operator/issues/104 (and no, I’ve only use vault-secrets-operator)
-
Automation assistants: GitOps tools in comparison
If you are using an external KMS in any case, then there are other options, such as the kubernetes-external-secrets operator that was originally started by GoDaddy and the externalsecret-operator from Container Solutions. If you use HashiCorp Vault, you also have the option of using the Vault Secrets operator. This works similarly to the Sealed Secrets Operator, but instead of managing its own key material, it retrieves the secrets from Vault. The CNCF Technology Radar from January 2021 provides an overview of the types of tools that are available for secrets management.
What are some alternatives?
helm-teller - Allows you to manage configuration and secrets from multiple provider while masking the secrets at the deployment
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
datahub-helm - Repository of helm charts for deploying DataHub on a Kubernetes cluster
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
configmapsecrets - A Kubernetes controller to manage configs with a mix of secret and non-secret data
sops - Simple and flexible tool for managing secrets
Reloader - A Kubernetes controller to watch changes in ConfigMap and Secrets and do rolling upgrades on Pods with their associated Deployment, StatefulSet, DaemonSet and DeploymentConfig – [✩Star] if you're using it!
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
Flux - Successor: https://github.com/fluxcd/flux2
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
atlantis - Terraform Pull Request Automation
argocd-vault-replacer - An Argo CD plugin to replace placeholders in Kubernetes manifests with secrets stored in Hashicorp Vault.