<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Terraform on LEMINNOV Blog</title>
    <link>/tags/terraform/</link>
    <description>Recent content in Terraform on LEMINNOV Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 07 Jul 2026 14:00:00 +0100</lastBuildDate>
    <atom:link href="/tags/terraform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Terranetes: Running Terraform Inside Kubernetes Architecture, Workflow, and Why It Matters</title>
      <link>/posts/terranetes/</link>
      <pubDate>Tue, 07 Jul 2026 14:00:00 +0100</pubDate>
      <guid>/posts/terranetes/</guid>
      <description>&lt;h1 id=&#34;terranetes-running-terraform-inside-kubernetes&#34;&gt;Terranetes: Running Terraform Inside Kubernetes&lt;/h1&gt;&#xA;&lt;p&gt;Developers need cloud resources an S3 bucket for uploads, a managed database for a new microservice, a message queue for event processing. The Terraform modules already exist. The infrastructure patterns are well-defined. But the provisioning path still looks like this: open a ticket, wait for a platform engineer, schedule a review, merge the PR, hope nothing drifts before the next audit.&lt;/p&gt;&#xA;&lt;p&gt;Meanwhile, the application side of the house ships multiple times a day through GitOps. The gap between &amp;ldquo;I need a database&amp;rdquo; and &amp;ldquo;here is your database&amp;rdquo; can be days not because the work is hard, but because the process was never designed for self-service.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
