<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secret on (Dev)Ops observations</title><link>https://ylitalot.com/categories/secret/</link><description>Recent content in Secret on (Dev)Ops observations</description><generator>Hugo</generator><language>en</language><copyright>Juha Ylitalo &amp;lt;juha@ylitalot.net&amp;gt;</copyright><lastBuildDate>Tue, 17 Nov 2026 12:00:00 +0200</lastBuildDate><atom:link href="https://ylitalot.com/categories/secret/index.xml" rel="self" type="application/rss+xml"/><item><title>SOPS for Secrets in GitOps</title><link>https://ylitalot.com/posts/sops-age/</link><pubDate>Tue, 17 Nov 2026 12:00:00 +0200</pubDate><guid>https://ylitalot.com/posts/sops-age/</guid><description>&lt;p&gt;Secrets are something that you usually need in one form or another when you deploy services into kubernetes cluster.&#10;One can easily add them with &lt;code&gt;kubectl apply ...&lt;/code&gt; to your kubernetes, but you don&amp;rsquo;t want to commit secrets as plain text&#10;into git repositories, which is a problem if you want to use GitOps to manage cluster.&lt;/p&gt;&#10;&lt;p&gt;Kubernetes has number of options that you can use to keep your secrets sealed secrets, external secrets, &amp;hellip;&#10;but SOPS with age is probably the easiest one to encrypt them in such way that you feel confident to save them&#10;into git repository.&lt;/p&gt;</description></item></channel></rss>