Deliver secrets to Kubernetes pods without storing in etcd, using VSO

Published: 2 days ago (December 16, 2025 at 10:00 AM EST)

1 min read

Source: HashiCorp Blog

Vault Secrets Operator (VSO)

Vault Secrets Operator (VSO) has simplified secrets management between HashiCorp Vault and Kubernetes by automatically syncing secrets from Vault into Kubernetes Secret objects. This approach fits naturally into existing Kubernetes patterns, but it also has a tradeoff: with the default VSO workflow,…

Back to Blog

Gateway API no EKS: O que muda com o fim do NGINX Ingress Controller

Se você usa EKS, provavelmente expõe aplicações com NGINX Ingress Controller e/ou AWS Load Balancer Controller usando Ingress tradicional. Mas há uma mudança im...

Adafruit: Arduino’s Rules Are ‘Incompatible With Open Source’

The open source hardware community is debating Arduino’s new Terms and Conditions following the company’s acquisition of Qualcomm. Chief microcontroller The pos...

HashiCorp year in review 2025: Lessons in simplifying the cloud

With 2025 winding to a close, we've been reflecting on what we’ve learned and done this year. Across hundreds of customer conversations this year, the themes ha...

day4: kube scheduler

Overview The Kubernetes scheduler decides which node each pod should run on. It does not place the pods itself; instead, it records the target node for each po...

Vault Secrets Operator (VSO)

Related posts

Gateway API no EKS: O que muda com o fim do NGINX Ingress Controller

Adafruit: Arduino’s Rules Are ‘Incompatible With Open Source’

HashiCorp year in review 2025: Lessons in simplifying the cloud

day4: kube scheduler