<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows-Containers on GeekyRyan</title><link>https://rnemeth90.github.io/tags/windows-containers/</link><description>Recent content in Windows-Containers on GeekyRyan</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 26 Nov 2025 09:00:00 +0000</lastBuildDate><atom:link href="https://rnemeth90.github.io/tags/windows-containers/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating a Legacy Windows API Service into Kubernetes</title><link>https://rnemeth90.github.io/projects/2025-11-26-migrating-a-legacy-api-to-kubernetes/</link><pubDate>Wed, 26 Nov 2025 09:00:00 +0000</pubDate><guid>https://rnemeth90.github.io/projects/2025-11-26-migrating-a-legacy-api-to-kubernetes/</guid><description>&lt;p&gt;Legacy ASP.NET Framework API service running in IIS on Windows VMs. Need to move it to Kubernetes for better scaling and cost efficiency.&lt;/p&gt;&#10;&lt;p&gt;The catch: this isn&amp;rsquo;t a modern cloud-native app that containerizes trivially. It&amp;rsquo;s full-framework, IIS-hosted. Containerized it as a Windows container with self-hosted OWIN instead of keeping IIS in the container - smaller footprint, less dependencies.&lt;/p&gt;&#10;&lt;p&gt;Windows Kubernetes migrations are different from Linux/.NET Core ones. Different tooling, larger images, longer startup times, Windows node pools. Don&amp;rsquo;t assume Linux Kubernetes knowledge transfers - Windows containers are a different ecosystem.&lt;/p&gt;</description></item></channel></rss>