#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
Lookonchain | ꘜ
Whales are accumulating $BGB recently.
0x8900 withdrew 192,668 $BGB($936K) from #Bitget over the past 2 months.
0x171D withdrew 30,607 $BGB($134K) from #Bitget 2 days ago.
0x7C9C withdrew 20,980 $BGB($102K) from #Bitget over the past 3 months.
Notably, #Bitget has burned a total of 860M $BGB($5.25B) over the past 8 months, reducing the total supply by 43%.
https://intel.arkm.com/explorer/address/0x89006C3aADfF87c5113b835660E3459C6Ad61F16
https://intel.arkm.com/explorer/address/0x171D1285a9a8De3f16d4c45706d4E2F4A5C9e175
https://intel.arkm.com/explorer/address/0x7C9C4f9046ba2173fae539FE62eEFAb1aBAD1523