<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>gitops on Oleksandr Kulbida</title>
    <link>https://okulbida.com/tags/gitops/</link>
    <description>Recent content in gitops on Oleksandr Kulbida</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Fri, 08 May 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://okulbida.com/tags/gitops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Terraform at scale: GitOps tools and the long apply problem</title>
      <link>https://okulbida.com/posts/terraform-gitops-state-management-alternatives/</link>
      <pubDate>Fri, 08 May 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/terraform-gitops-state-management-alternatives/</guid>
      <description>If you&amp;rsquo;ve been using Terraform Cloud for a while, you&amp;rsquo;ve probably hit at least one of these: the pricing model changed and suddenly it&amp;rsquo;s expensive, applies take 10+ minutes, or the state files have grown into something nobody wants to touch. You&amp;rsquo;re not alone — this is a recurring topic in every DevOps community right now.
This post covers the main tools people are using to solve these problems in 2025–2026, with a focus on two separate issues that often get conflated: GitOps orchestration (who triggers plans, who approves applies) and state management at scale (why applies are slow and what to do about it).</description>
    </item>
    
  </channel>
</rss>
