<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/kubernetes/</link><description>Recent content in Kubernetes on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 23 Jun 2023 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker and Containers (8): Beyond Docker — Kubernetes, Swarm, and What Comes Next</title><link>https://www.chenk.top/en/docker-containers/08-orchestration-preview/</link><pubDate>Fri, 23 Jun 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/docker-containers/08-orchestration-preview/</guid><description>&lt;p>So far, this series has focused on single-host Docker: one machine running containers. This setup works well for development, small projects, and applications with modest traffic. However, when you need your service to survive server failures, handle traffic spikes, or deploy updates without downtime, single-host Docker falls short. Container orchestration addresses these issues, and Kubernetes has become the go-to solution.&lt;/p>
&lt;hr>
&lt;h2 id="why-single-host-docker-isnt-enough" class="heading-anchor">Why Single-Host Docker Isn&amp;rsquo;t Enough&lt;a href="#why-single-host-docker-isnt-enough" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>Consider what happens when your Docker host fails:&lt;/p></description></item><item><title>Cloud Computing (3): Cloud-Native and Container Technologies</title><link>https://www.chenk.top/en/cloud-computing/cloud-native-containers/</link><pubDate>Sat, 11 Mar 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/cloud-computing/cloud-native-containers/</guid><description>&lt;p>&lt;figure class="article-figure">
 &lt;img src="https://blog-pic-ck.oss-cn-beijing.aliyuncs.com/posts/en/cloud-computing/cloud-native-containers/illustration_1.png" alt="Cloud Computing (3): Cloud-Native and Container Technologies — Chapter overview" loading="lazy" decoding="async" class="content-image">
 
&lt;/figure>
&lt;/p>
&lt;p>The shift from monolithic applications to cloud-native architectures is one of the most consequential changes in software engineering this decade. The headline — containers and Kubernetes — is well known. The interesting story is &lt;em>why&lt;/em> this stack won, what each layer actually does, and where the seams are that determine whether your platform feels effortless or feels like a maze.&lt;/p></description></item></channel></rss>