<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vadim Poyaskov</title><link>https://poyaskov.ca/</link><description>Recent content on Vadim Poyaskov</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 15 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://poyaskov.ca/index.xml" rel="self" type="application/rss+xml"/><item><title>GitOps in Practice: ArgoCD + GitHub Actions at Scale</title><link>https://poyaskov.ca/blogs/gitops-with-argocd-and-github-actions/</link><pubDate>Wed, 15 Jul 2026 00:00:00 +0000</pubDate><guid>https://poyaskov.ca/blogs/gitops-with-argocd-and-github-actions/</guid><description>&lt;p&gt;At Backbase, we operate a Banking-as-a-Service platform that serves 150+ banks and credit unions. That means running Kubernetes clusters for each customer — across Azure AKS and AWS EKS — and deploying to all of them reliably, repeatedly, and safely.&lt;/p&gt;
&lt;p&gt;This post covers how we do it with &lt;strong&gt;ArgoCD&lt;/strong&gt; and &lt;strong&gt;GitHub Actions&lt;/strong&gt;, and the lessons we&amp;rsquo;ve learned along the way.&lt;/p&gt;
&lt;h2 id="the-core-idea"&gt;The Core Idea&lt;/h2&gt;
&lt;p&gt;GitOps is simple in principle: Git is the single source of truth. Every change to infrastructure or application config goes through a pull request. The cluster reconciles itself to match what&amp;rsquo;s in Git.&lt;/p&gt;</description></item></channel></rss>