<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secrets Management on DefinIT</title><link>https://www.definit.co.uk/tag/secrets-management/</link><description>Recent content in Secrets Management on DefinIT</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026</copyright><lastBuildDate>Tue, 28 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.definit.co.uk/tag/secrets-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Vault Secrets in Kubernetes</title><link>https://www.definit.co.uk/2026/07/vault-secrets-in-kubernetes/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.definit.co.uk/2026/07/vault-secrets-in-kubernetes/</guid><description>&lt;p&gt;I run &lt;a href="https://argoproj.github.io/cd/" target="_blank" rel="noreferrer"&gt;ArgoCD&lt;/a&gt; or &lt;a href="https://fluxcd.io/" target="_blank" rel="noreferrer"&gt;Flux&lt;/a&gt; on my Kubernetes clusters to manage everything with GitOps - every configuration is committed to Git before being applied to the cluster by Argo/Flux. Secrets don&amp;rsquo;t fit that model quite so neatly, and this post is about how I&amp;rsquo;m using HashiCorp Vault, and specifically the Vault Secrets Operator (VSO), to bring them into it.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://www.definit.co.uk/2026/07/vault-secrets-in-kubernetes/featured.png"/></item></channel></rss>