
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>clusternotes.io</title>
      <link>https://clusternotes.io/blog</link>
      <description>Notes from a cloud-native engineering journey — Kubernetes, observability, GitOps, Azure, AWS. Practical lessons, hands-on experiments, and how the pieces actually fit together.</description>
      <language>en-us</language>
      <managingEditor>kozlowski.softnet@gmail.com (Krzysztof Kozłowski)</managingEditor>
      <webMaster>kozlowski.softnet@gmail.com (Krzysztof Kozłowski)</webMaster>
      <lastBuildDate>Thu, 14 May 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://clusternotes.io/tags/security/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://clusternotes.io/blog/zero-secrets-azure-workload-identity</guid>
    <title>Stop shipping secrets in Git — the AKS Workload Identity + External Secrets pattern I use</title>
    <link>https://clusternotes.io/blog/zero-secrets-azure-workload-identity</link>
    <description>Kubernetes Secrets are base64, not encrypted. Here is the full path I use to keep zero secret material inside the cluster — Workload Identity federates a pod to a managed identity, External Secrets Operator pulls live values from Key Vault. Terraform, manifests, pitfalls, all of it.</description>
    <pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
    <author>kozlowski.softnet@gmail.com (Krzysztof Kozłowski)</author>
    <category>azure</category><category>kubernetes</category><category>security</category>
  </item>

    </channel>
  </rss>
