Deep dive on External Secrets Operator with Vault & using other providers

Join John and Fred live for a new livestream on our deep dive series. This time, we will discuss External Secrets Operator (ESO) used in collaboration with HashiCorp Vault within kubefirst. We will also explore the possibilities to use other providers if Vault doesn't suit your needs.
--
Kubefirst is a free & open source tool which delivers instant GitOps platforms so you can have the most popular open source tools working together in minutes within your new Kubernetes cluster.
External Secrets Operator: github.com/ext...
Learn more: kubefirst.io
Join our Slack community: kubefirst.io/s...
#kubernetes #cloudnative #opensource #gitops #devops

[@JohnDietz1]

free tee shirt for anyone who guesses correctly how many times i said "important distinction" in this one 😂

[@kubefirst]

Let's do that!

[@SanjeevKumar-nq8td]

How does it differ from Hasicorp Vault Secret Operator, Can it be swapped with External Secret Operator

[@kubefirst]

The External Secrets Operator (ESO) and Vault Operator both make secrets available to your Kubernetes cluster from a Vault secret store backend. The HashiCorp Vault one only work with Vault. ESO works with multiple different secret backends, which makes it a much more technology-agnostic secret abstraction layer for your platform in our opinion. Check external-secrets.io/latest/api/secretstore/ for more information.