100,000 Different Ways to Manage Secrets in GitOps - Andrew Block, Red Hat

100,000 Different Ways to Manage Secrets in GitOps - Andrew Block, Red Hat
Any GitOps implementation involves managing a wide range of resources. Sooner rather than later, there will become a need to manage sensitive assets, such as passwords or tokens. So, how can these types of assets be handled appropriately so that they are not visible in plain text when stored in a Git repository? Secrets management is a prevalent topic in the cloud native ecosystem and given its importance, tools and frameworks have been developed that can be applied to not only the content itself, but also within GitOps engines. Understanding where, how and when they can be used could make all the difference when employing proper security measures while implementing a GitOps solution. Attendees will learn: * Tools for detecting the presence of sensitive assets within Git repositories * Strategies for encrypting data at rest * Integrations with purpose built secrets management engines * How sensitive assets can be stored and used when working with public cloud providers * The mechanisms for which GitOps engines can aid in the management of sensitive resources Upon completion, attendees will no longer have an excuse to leave sensitive assets unprotected again!

[@etemcitil]

most comprehensive secret management session

[@gouravchhabra6142]

Sealed secret's CLI tool is called Kubeseal not kubeval.

[@PatrickMetzdorf]

Ok this is very interesting, but the talk should really have been named "Several ways to manage secrets in Kubernetes", as it has little to do with GitOps and primarily about general secret management tools and how to use them from Kubernetes projects.