<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containers on Ikwuka Okoye</title><link>https://ikwukao.dev/tags/containers/</link><description>Recent content in Containers on Ikwuka Okoye</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 11 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ikwukao.dev/tags/containers/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Platform-Infra: Using Terraform to Manage Local Kubernetes Infrastructure</title><link>https://ikwukao.dev/journal/platform-infra-terraform-kubernetes/</link><pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate><guid>https://ikwukao.dev/journal/platform-infra-terraform-kubernetes/</guid><description>&lt;h2 id="building-platform-infra-using-terraform-to-manage-local-kubernetes-infrastructure"&gt;Building Platform-Infra: Using Terraform to Manage Local Kubernetes Infrastructure&lt;/h2&gt;
&lt;p&gt;Infrastructure becomes difficult to reason about when environments are created through a collection of undocumented commands.&lt;/p&gt;
&lt;p&gt;That problem becomes even more noticeable when several services, containers, configuration files, namespaces, and deployment steps are involved.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Platform-Infra&lt;/strong&gt; started from that observation.&lt;/p&gt;
&lt;p&gt;The project is a master orchestration repository designed to manage the infrastructure and deployment configuration surrounding my backend services using Infrastructure as Code principles.&lt;/p&gt;</description></item></channel></rss>