<?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 - architecture</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/architecture/rss.xml" rel="self" type="application/rss+xml"/>
      <lastBuildDate>Sun, 05 Jul 2026 00:00:00 +0000</lastBuildDate>
      <item>
          <title>K8s &amp; OpenShift: The Big Picture</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-overview/</link>
          <guid>https://blog.none.at/blog/2026/2026-07-01-k8s-openshift-bp-overview/</guid>
          <description xml:base="https://blog.none.at/blog/2026/2026-07-01-k8s-openshift-bp-overview/">&lt;p&gt;This is the opening post of a seven-part series on Kubernetes and OpenShift best practices, written
from the vantage point of 2026 and eight years of hands-on experience — from initial cluster design
through Day-2 operations and production debugging. This first part is deliberately non-technical: it is about &lt;em&gt;whether&lt;&#x2F;em&gt;
and &lt;em&gt;when&lt;&#x2F;em&gt; a container platform earns its keep — the decisions that happen before anyone writes a
single YAML manifest.&lt;&#x2F;p&gt;</description>
      </item>
    </channel>
</rss>
