<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GHCR on Igor Baiborodine</title>
    <link>https://www.kiroule.com/tags/ghcr/</link>
    <description>Recent content in GHCR on Igor Baiborodine</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 29 Apr 2026 08:08:23 -0400</lastBuildDate>
    <atom:link href="https://www.kiroule.com/tags/ghcr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From Push to Pull: Completing Insurance Hub Phase 1 with CI/CD and GitOps</title>
      <link>https://www.kiroule.com/article/from-push-to-pull-completing-insurance-hub-phase-1-with-github-actions-and-flux/</link>
      <pubDate>Mon, 20 Apr 2026 08:00:00 -0400</pubDate>
      <guid>https://www.kiroule.com/article/from-push-to-pull-completing-insurance-hub-phase-1-with-github-actions-and-flux/</guid>
      <description>&lt;p&gt;The previous &lt;a href=&#34;https://www.kiroule.com/article/lift-completed-now-shift-making-the-insurance-hub-kubernetes-native-enough/&#34;&gt;article&lt;/a&gt;&#xA;concluded with the system successfully running on Kubernetes, yet it still relied on a manual&#xA;deployment model. While validating the cluster foundation and service manifests was a significant&#xA;milestone, it also revealed a lingering operational gap: the platform had a Kubernetes runtime, but&#xA;it lacked a Kubernetes-native delivery process.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
