Nicolas Vibert’s Post

Coming out next week: a fun "Kubernetes Networking and Cilium" eBook, written by a network engineer for network engineers. This is the book I wish I had when I started to learn about Kubernetes. Explained in terms and references network engineers will understand, the eBook will still be accessible to anyone keen to learn about Kubernetes networking and the de facto cloud-native networking platform: Cilium. Including answers to the following: 🔧 What We Need The Network To Do 🔗 Kubernetes Networking Fundamentals 🔹 Introducing Cilium 💻 Where is my CLI? ⚙️ How do I configure Kubernetes and Cilium? 🖧 Where is my DHCP Server? 🔍 What is a Kubernetes namespace? 🔎 Where is my DNS Server? 🔍 How Do Pods Talk To Each Other? 🔍 Kubernetes Metadata 🏷️ What's a Label? 📝 What's an Annotation? 🔒 How do I secure my cluster? 🔐 What's identity-based security? 🔥 Where's my Layer 7 firewall? 🔥 Where's my Load Balancer? 🔄 How do I load balance traffic within the cluster? 🔄 How do I load balance traffic entering the cluster? 🌐 Where's my web proxy? 🔌 How can I connect my cluster to existing networks? 🔌 I don't have any BGP-capable device in my existing network. Is there another way for me to access my Kubernetes services? 🔐 How do I connect my cluster with an external firewall? 🔐 How do internal Load Balancing and NAT work under the hood? 🔍 How do I manage and troubleshoot my network? 🔍 How can I monitor and visualize network traffic? 🔒 How do I start securing my cluster? 🔐 How do I encrypt the traffic in my cluster? 🔄 How do we connect clusters together? 🌐 Is IPv6 supported on Kubernetes? 📊 Does the concept of Quality of Service (QoS) exist in Kubernetes? 🔌 Which Kubernetes networking options are available in managed Kubernetes services? Hope you find it useful!

Lots of cool updates on the Isovalent Hands-on labs. We are seeing a spike of Cisco folks taking labs which might explain why we’re seeing record numbers of labs (>1,400 a week). Warning though - these labs are pretty addictive!!

Amit Gupta has tested and documented so many Cilium features and use cases in the past year. This time he’s providing an in-depth look at IPv4/IPv6 Dual Stack on AKS 👏🏾

Officially back at Cisco, after 3,256 days away. Can't wait to catch up with old friends, to make new ones, and to keep working with the awesome Isovalent team. https://lnkd.in/eRFtAv6e

I see Raphaël Pinson and myself in the video - we both are big fans of Instruqt and that’s what I used for my demos and how we’ve been teaching thousands of engineers how to use Cilium.

Here is my recap of KubeCon Paris, a 3-day long event that sometimes felt like a month but also went too quickly 🤷🏾♂️ While I cover technology trends and Cilium & eBPF highlights, I also go behind the scenes of being a sponsor 💸 and a speaker 😨 And I reveal what Solomon Hykes said during his keynote 😅 Let me know what you think! https://lnkd.in/e-_kspsH

Thanks to Isaac Sacolick for quoting me in his "Root Cause Analysis" article on InfoWorld. Rightly or wrongly, the network is always blamed when we observe issues with our applications. Let me make the case that our performance justice system should have a presumption of innocence. How do we prove the network is guilty? I would argue that eBPF can provide so much context on how applications behave that using Cilium is like finding matching DNA evidence at the crime scene. OK - I'll stop the legal parallels (you can see I've been watching too many courtroom drama on TV) but you can read the full article here: https://lnkd.in/djujK-pQ

To the 1,600+ people who signed up for our Cilium introduction session at KubeCon last week: are you all mad?! Why didn't you go to AI sessions instead of one on boring old networking?! 😝 To the 300 folks who managed to squeeze into the room: thank you! We hope you got a lot out of it. To my co-presenter Daniel Finneran: thank you for the laughs and all the work you put into the presentation. It was fun! The intention of the session was: - Acknowledge that networking can be hard - Explain Kubernetes networking without jargon and acronyms - Walk through the core Kubernetes networking requirements and how Cilium can take care of most of them - Demo in 10 minutes three use cases - network policy, observability and Gateway API load-balancing You can watch the session here - let me know what you think! https://lnkd.in/eTfcw_dY

Thanks C. Thomas (Tom) Smith, III for publishing our Q&A on Cilium, or, as I’d like to call it, the de facto Kubernetes Networking Layer.