
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Tech, Startups &amp; I</title>
      <link>https://aniljaiswal.com/blog</link>
      <description>I build products and infrastructure, think about startups, and occasionally ride motorcycles. This is where I write.</description>
      <language>en-us</language>
      <managingEditor>er.anil.jaiswal@gmail.com (Anil Jaiswal)</managingEditor>
      <webMaster>er.anil.jaiswal@gmail.com (Anil Jaiswal)</webMaster>
      <lastBuildDate>Wed, 15 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://aniljaiswal.com/tags/supply-chain/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://aniljaiswal.com/blog/shipping-updates-into-air-gapped-environments</guid>
    <title>Shipping Software Updates Into an Air-Gapped Environment</title>
    <link>https://aniljaiswal.com/blog/shipping-updates-into-air-gapped-environments</link>
    <description>In a regulated or air-gapped deployment your CI/CD pipeline stops at the customer&#39;s firewall. Here is how you actually get a signed, verifiable update to a box you cannot reach, and keep it patchable for years.</description>
    <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
    <author>er.anil.jaiswal@gmail.com (Anil Jaiswal)</author>
    <category>air-gapped</category><category>enterprise-deployment</category><category>supply-chain</category><category>devsecops</category><category>kubernetes</category>
  </item>

    </channel>
  </rss>
