<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Kubernetes on nublog</title><link>https://nublog.pages.dev/tags/kubernetes/</link><description>Recent content in Kubernetes on nublog</description><generator>Hugo -- 0.160.0</generator><language>en-us</language><lastBuildDate>Sat, 28 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nublog.pages.dev/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>From Docker Compose to Kubernetes: Modernizing My Spring Boot API</title><link>https://nublog.pages.dev/posts/my-fourth-post/</link><pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate><guid>https://nublog.pages.dev/posts/my-fourth-post/</guid><description>&lt;p&gt;In my previous post, I shared how I built Treso, a secure expense tracking REST API using Spring Boot, and deployed it using Docker and AWS EC2. While that setup worked great, managing containers with manual &lt;code&gt;docker run&lt;/code&gt; commands and custom networks isn&amp;rsquo;t how large-scale cloud applications operate today.&lt;/p&gt;
&lt;p&gt;To level up my infrastructure skills, I decided to migrate Treso to a fully Cloud-Native architecture using &lt;strong&gt;Kubernetes&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This post covers my journey from imperative container management to declarative orchestration.&lt;/p&gt;</description></item></channel></rss>