<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Openbao on Cloud Native &amp; Open Source: A Team Lead’s Working Journal</title>
    <link>https://www.msbiro.net/tags/openbao/</link>
    <description>Recent content in Openbao on Cloud Native &amp; Open Source: A Team Lead’s Working Journal</description>
    <image>
      <title>Cloud Native &amp; Open Source: A Team Lead’s Working Journal</title>
      <url>https://www.msbiro.net/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://www.msbiro.net/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.164.0</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 17 Jul 2026 06:30:00 +0100</lastBuildDate>
    <atom:link href="https://www.msbiro.net/tags/openbao/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>In 2026 I Am Still Asked Why You Need a Centralized Secrets Manager</title>
      <link>https://www.msbiro.net/posts/secrets-manager-catalog-2026-non-negotiable/</link>
      <pubDate>Fri, 17 Jul 2026 06:30:00 +0100</pubDate>
      <guid>https://www.msbiro.net/posts/secrets-manager-catalog-2026-non-negotiable/</guid>
      <description>Why a centralized secrets manager is non-negotiable in 2026: the operational limits of git-crypt and sealed-secrets style tools, the DORA and NIS2 mandate, and why OpenBao is now the open source secrets manager to adopt.</description>
    </item>
  </channel>
</rss>
