Best Methods for Managing Secrets in Production Kubernetes

0
8
Asked By CuriousCactus79 On

Hi there! I'm currently setting up a production-grade Kubernetes cluster on AWS using EC2 and RKE2. I'm looking for recommendations on the most secure way to manage secrets using AWS Secret Manager. Should I go with the External Secrets Operator (ESO) or the Secret CSI Driver? Also, how does HashiCorp Vault compare in terms of security and usability? Right now, I'm just storing database credentials, but I plan to include more sensitive data in the future. I'd love your insights!

3 Answers

Answered By CloudNinja88 On

I switched to the Doppler Kubernetes Operator and it's been a game changer for managing secrets. You should definitely check it out – it might fit your needs better.

Answered By CodeWhisperer45 On

Honestly, I'm not a fan of how the Secret CSI Driver works. It's really slow and cumbersome for handling secrets, which can be frustrating in a production environment.

Answered By TechLover22 On

I've been using the External Secrets Operator with AWS Secrets Manager and EKS via Rancher in my production setup. It integrates well with GitHub Actions for automation; my dev team utilizes GitHub secrets to push into AWS Secrets Manager. The ESO simplifies pulling secrets for every deployment, which is especially handy when managing multiple clusters under a single tenant.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.