<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multi-Service on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/multi-service/</link><description>Recent content in Multi-Service on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 12 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/multi-service/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 13: Project 2: Deploying a Multi-Service Application to Kubernetes</title><link>https://ai-blog.noorshomelab.dev/devops-journey-2026/project-multi-service-kubernetes/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/devops-journey-2026/project-multi-service-kubernetes/</guid><description>&lt;h2 id="chapter-13-project-2-deploying-a-multi-service-application-to-kubernetes"&gt;Chapter 13: Project 2: Deploying a Multi-Service Application to Kubernetes&lt;/h2&gt;
&lt;p&gt;Welcome back, future DevOps guru! In our previous Kubernetes adventures, we learned about the fundamental building blocks like Pods, Deployments, and Services. We even deployed a single application. But what happens when your application isn&amp;rsquo;t just one component, but a collection of interconnected services, like a frontend web app talking to a backend API, which might then talk to a database?&lt;/p&gt;</description></item></channel></rss>