<?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 Youssef El Jirari</title><link>https://eljirari.me/tags/kubernetes/</link><description>Recent content in kubernetes on Youssef El Jirari</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 30 Aug 2023 22:53:30 +0100</lastBuildDate><atom:link href="https://eljirari.me/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Cilium vs Calico vs Flannel: Choose the Network You Can Operate</title><link>https://eljirari.me/posts/kubernetes-cni/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://eljirari.me/posts/kubernetes-cni/</guid><description>When people compare Kubernetes CNIs, the discussion quickly becomes a feature matrix.
Does it support NetworkPolicy? BGP? eBPF? Encryption? Observability?
Those are useful questions, but I think they miss the first one:
What networking problem does this cluster actually need the CNI to solve?
A three-node K3s cluster and a large multi-tenant Kubernetes platform do not need the same network architecture.
Start with what the CNI does A pod needs an IP address and it needs to communicate with other pods.</description></item><item><title>Containers: The Backstory</title><link>https://eljirari.me/posts/containers-thebackstory/</link><pubDate>Wed, 30 Aug 2023 22:53:30 +0100</pubDate><guid>https://eljirari.me/posts/containers-thebackstory/</guid><description>Back in my student days, I first bumped into Docker. It was all the rage then, and honestly, it blew my mind. The idea that you could take a piece of code, make it work anywhere in its own little space, separate from the computer&amp;rsquo;s main system – that was pretty cool. Later on, I found out Docker wasn&amp;rsquo;t the first to come up with this container and isolation stuff. In this blog post, I want to take you on a little trip back in time to check out who started it all.</description></item></channel></rss>