<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Naveenchand R B — Blog</title>
    <link>https://naveenops.com/blog/</link>
    <description>Notes on DevSecOps, Kubernetes, platform engineering and the parts of getting to production that are easy to get wrong.</description>
    <language>en</language>
    <atom:link href="https://naveenops.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Wed, 14 Oct 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Sign every image, then refuse the ones that are not signed</title>
      <link>https://naveenops.com/blog/sample-signing-every-image/</link>
      <guid isPermaLink="true">https://naveenops.com/blog/sample-signing-every-image/</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
      <description>Signing artifacts is the easy half. The half that changes anything is the admission controller that turns an unsigned image into a failed deploy.</description>
      <category>Supply chain</category>
      <category>Kubernetes</category>
      <category>Policy</category>
    </item>
    <item>
      <title>Alerts worth waking up for</title>
      <link>https://naveenops.com/blog/sample-alerts-worth-waking-for/</link>
      <guid isPermaLink="true">https://naveenops.com/blog/sample-alerts-worth-waking-for/</guid>
      <pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate>
      <description>Most alerting rules measure the system. The useful ones measure whether anybody is having a bad time, which is a much shorter list.</description>
      <category>Observability</category>
      <category>SRE</category>
      <category>OpenTelemetry</category>
    </item>
  </channel>
</rss>
