<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
      <title>Alek&#x27;s Blog - network-policy</title>
      <link>https://blog.none.at</link>
      <description>Production notes on Kubernetes, OpenShift, and OVHcloud: observability, log archiving, service mesh, LLM inference, and digital sovereignty.</description>
      <generator>Zola</generator>
      <language>en</language>
      <atom:link href="https://blog.none.at/tags/network-policy/rss.xml" rel="self" type="application/rss+xml"/>
      <lastBuildDate>Wed, 01 Jul 2026 00:00:00 +0000</lastBuildDate>
      <item>
          <title>K8s &amp; OpenShift: Security</title>
          <pubDate>Wed, 01 Jul 2026 00:00:00 +0000</pubDate>
          <author>aleks</author>
          <link>https://blog.none.at/blog/2026/2026-07-01-k8s-openshift-bp-security/</link>
          <guid>https://blog.none.at/blog/2026/2026-07-01-k8s-openshift-bp-security/</guid>
          <description xml:base="https://blog.none.at/blog/2026/2026-07-01-k8s-openshift-bp-security/">&lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;blog.none.at&#x2F;blog&#x2F;2026&#x2F;2026-07-01-k8s-openshift-bp-scaling&#x2F;&quot;&gt;Part 4&lt;&#x2F;a&gt; covered scaling and resilience.
This part covers security — not as a checklist to complete before an audit, but as a set of
controls that reduce real attack surface and limit the blast radius when something goes wrong.&lt;&#x2F;p&gt;</description>
      </item>
    </channel>
</rss>
