<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>On-Premises on LEMINNOV Blog</title>
    <link>/tags/on-premises/</link>
    <description>Recent content in On-Premises on LEMINNOV Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jun 2026 15:01:35 +0300</lastBuildDate>
    <atom:link href="/tags/on-premises/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building a Modern On-Premises OpenShift Platform: GitOps, Operators, Zero Trust, Observability and AI</title>
      <link>/posts/openshift-enterprise-platform/</link>
      <pubDate>Fri, 19 Jun 2026 15:01:35 +0300</pubDate>
      <guid>/posts/openshift-enterprise-platform/</guid>
      <description>&lt;h1 id=&#34;building-a-modern-on-premises-openshift-platform&#34;&gt;Building a Modern On-Premises OpenShift Platform&lt;/h1&gt;&#xA;&lt;p&gt;A while back, a customer came to us with a familiar tension: they wanted the speed of the cloud — self-service, automation, ship whenever you&amp;rsquo;re ready — but their data wasn&amp;rsquo;t allowed to leave the building. Regulated industry, strict sovereignty rules, auditors who ask hard questions.&lt;/p&gt;&#xA;&lt;p&gt;So we built them an OpenShift platform that lives entirely inside their own datacenter, yet still feels like a modern cloud to the people using it. GitOps, CI/CD, single sign-on, observability, multi-cluster governance, even model serving for the data-science team — all of it running on hardware they own and control.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
