<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on Ikwuka Okoye</title><link>https://ikwukao.dev/tags/devops/</link><description>Recent content in DevOps 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/devops/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><item><title>Designing OpsPilot: Building a Modular DevOps Operations Toolkit</title><link>https://ikwukao.dev/journal/designing-opspilot/</link><pubDate>Mon, 10 Aug 2026 00:00:00 +0000</pubDate><guid>https://ikwukao.dev/journal/designing-opspilot/</guid><description>&lt;h2 id="designing-opspilot-building-a-modular-devops-operations-toolkit"&gt;Designing OpsPilot: Building a Modular DevOps Operations Toolkit&lt;/h2&gt;
&lt;p&gt;As backend systems become more complex, the operational work surrounding them becomes increasingly difficult to ignore.&lt;/p&gt;
&lt;p&gt;Running services, inspecting environments, managing containers, checking infrastructure, and performing repetitive maintenance tasks can quickly turn into a collection of shell commands, scripts, and undocumented procedures.&lt;/p&gt;
&lt;p&gt;That was the problem I wanted to explore with &lt;strong&gt;OpsPilot&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Rather than building another collection of unrelated scripts, I wanted to create a structured operations toolkit that could grow alongside the systems it manages.&lt;/p&gt;</description></item><item><title>Building OpsPilot: Why I Started a DevOps Platform</title><link>https://ikwukao.dev/journal/building-opspilot/</link><pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate><guid>https://ikwukao.dev/journal/building-opspilot/</guid><description>&lt;p&gt;OpsPilot started with a simple question: &lt;strong&gt;what would happen if I built the operational tooling I kept wishing I had?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;As I continued working across backend engineering, DevOps, and cloud-native infrastructure, I found myself repeatedly dealing with the same categories of operational work. Instead of treating those tasks as isolated scripts and commands, I wanted to explore what it would look like to bring them together into a coherent engineering platform.&lt;/p&gt;</description></item><item><title>OpsPilot</title><link>https://ikwukao.dev/projects/opspilot/</link><pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate><guid>https://ikwukao.dev/projects/opspilot/</guid><description>A DevOps-focused engineering platform exploring automation, CLI design, container workflows, and cloud-native operations.</description></item></channel></rss>