vault-secrets-operator
git-blame-someone-else
vault-secrets-operator | git-blame-someone-else | |
---|---|---|
5 | 108 | |
611 | 10,642 | |
- | - | |
8.0 | 0.0 | |
9 days ago | 5 months ago | |
Go | Shell | |
MIT License | 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.
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.
git-blame-someone-else
- FTX "insurance fund" calculated by multiplying trading volume by random number
-
someThingsAreForever
Or be a crafty bastard and use git blame-someone-else
-
When is it OK to blame your colleague?
A tool for you: https://github.com/jayphelps/git-blame-someone-else
-
Git Blame-Someone-Else
But funny enough is that there is a commit where it pretends to be Linus https://github.com/jayphelps/git-blame-someone-else/commit/e...
- little does he know 😂
- Erros
-
How Git Blame Really Works
It can be!
-
(Dusj)tanke: Ansvarliggjøring av beslutningstakere ved eponymisering av lover / avgjørelser.
git blame someone else
- The small things that bring me joy when working late
What are some alternatives?
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
AmogOS - ඞ Among-us themed OS. As seen on Reddit and Youtube.
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
ioccc-obfuscated-c-contest - IOCCC International Obfuscated C code contest entries
sops - Simple and flexible tool for managing secrets
YiffSpot - A real-time web chat for "yiffing" randomly with other furries anonymously.
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
five - Gives you five
Flux - Successor: https://github.com/fluxcd/flux2
open-and-shut - Type in Morse code by repeatedly slamming your laptop shut
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
git-gud - Ever had someone tell you to "get good"? Now you can!