<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Github-Actions on Eliorion blog</title><link>https://eliorion.github.io/My-blog/tags/github-actions/</link><description>Recent content in Github-Actions on Eliorion blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 25 May 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://eliorion.github.io/My-blog/tags/github-actions/index.xml" rel="self" type="application/rss+xml"/><item><title>GitOps Without Kubernetes: Docker Compose + GitHub Actions</title><link>https://eliorion.github.io/My-blog/11---posts/2026-05-25---mve-itguard-gitops/</link><pubDate>Mon, 25 May 2026 09:00:00 +0200</pubDate><guid>https://eliorion.github.io/My-blog/11---posts/2026-05-25---mve-itguard-gitops/</guid><description>&lt;h2 id="gitops-is-a-principle-not-a-tool"&gt;GitOps Is a Principle, Not a Tool&lt;/h2&gt;
&lt;p&gt;When people talk about GitOps, Kubernetes quickly enters the conversation. FluxCD, ArgoCD, Helm — the ecosystem is rich, and the tooling handles a lot of the heavy lifting. The platform continuously watches the repository and reconciles the cluster state to match what Git declares.&lt;/p&gt;
&lt;p&gt;But the underlying principle has nothing to do with Kubernetes specifically. GitOps is simpler than that: &lt;strong&gt;Git is the single source of truth. No change happens outside of Git. Automation applies what Git declares.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>