GitHub Trends

#go#external_secrets#hacktoberfest#kubernetes#kubernetes_secrets#secrets_manager External Secrets Operator (ESO) is a Kubernetes tool that connects external secret managers like AWS Secrets Manager, HashiCorp Vault, and others to Kubernetes, automatically injecting secret values into Kubernetes Secrets. However, official releases are paused because the current maintainer team is too small to support ongoing development and community help. You can still use the latest code from the main branch, but no new official versions or support will be provided until more maintainers join. If your team relies on ESO, contributing helps keep the project healthy and ensures future updates. This pause highlights the importance of community support for open-source tools you depend on. Using ESO benefits you by simplifying secure secret management in Kubernetes across multiple cloud providers. https://github.com/external-secrets/external-secrets

#go#devops_workflow#encrypt_secrets#gitops#kubernetes#kubernetes_secrets Sealed Secrets is a tool for Kubernetes that lets you safely store sensitive information—like passwords or API keys—in your code repository by encrypting them so only your Kubernetes cluster can decrypt them. You use a tool called `kubeseal` to encrypt secrets on your computer, and then store the encrypted result in your repository. When you apply this encrypted secret to your cluster, a special controller inside Kubernetes decrypts it and creates a regular secret that your apps can use. This means you can manage all your configuration in Git, even secrets, without worrying about exposing sensitive data, and only the cluster itself can access the real secret[2][5][1]. The benefit is that your secrets are protected at every step, and you can use Git workflows for everything, making your setup more secure and easier to manage. https://github.com/bitnami-labs/sealed-secrets