By Kim Schlesinger and Daniel Hix
There are many ways to keep your application API keys, tokens, and passwords confidential in Kubernetes, but choosing the right technique can feel overwhelming.
Explore the benefits of using an external secrets provider like HashiCorp Vault. We’ll compare and contrast two techniques for using Vault to store and share secrets with a Kubernetes cluster. You’ll come away from this talk with a better understanding of how to use Vault to manage secrets in Kubernetes.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
I'm a developer advocate at DigitalOcean focusing on Kubernetes and other Cloud Native technologies
I build things at DigitalOcean that make storage in the cloud work, and specifically I work with Kubernetes to enable workload orchestration.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Managing Kubernetes Secrets: Comparing External Secrets Operator and Secrets Store CSI Driver | DigitalOcean