Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.
This week we’re going to talk about the next level of virtualization: the virtualization of virtualization itself.
1. We’ve been saying this for a long time; and lo and behold, Kubernetes clusters have officially become cattle by now. So much that, in fact, you can use vcluster to literally launch clusters inside other clusters. “It’s turtles all the way down”, they said. How many turtle levels can there be?
2. Keeping up with the “Kubernetes in Kubernetes” trend, here’s KinK which as the name (KinDa) suggests, consists in running KinD into (what else?) Kubernetes clusters. Please be KinD to your clusters. And if you’re more interested in k3s than KinD, may we tempt you with a free webinar about k3s next week?
3. If you are tired of running Kubernetes clusters into Kubernetes clusters, you can try to build a platform upon them; that’s what Syntasso Kratix does. Think of it as an internal PaaS for your own business, to ensure quick ans swift provisioning of cloud services to your internal teams.
4. Kubernetes in 2019 was inevitable; in 2021, it’s everywhere. Red Hat asked 202 CTOs and architects, and 94% of them are using Kubernetes in one way or another. Unfortunately, this also means that we’re going to see more and more Kubernetes-related security issues (like the recent one on Microsoft Azure) in the future.
Patch your software. The root cause here was running Kubernetes v1.8.4 (released Nov. 2017!!!) and runc 1.0.0-rc2 (released Oct. 2016!!!).— Dan Lorenc (@lorenc_dan) September 12, 2021
Both of these were ***years*** past their security fix EOL. https://t.co/QWmHKijy75
5. Security is not the only issue with Kubernetes; its power consumption patterns are a major threat for the planet. At a moment in which we all need to drastically and immediately reduce our carbon emissions, Kubernetes appears as an inappropriate choice. The community must work towards reducing its carbon footprint, and fast.
6. BONUS ITEM! Here’s 16 things you didn’t know about Kube APIs and CRDs. And as the article says, #15 is, indeed, shocking.
How could we make Kubernetes more climate-change friendly? How many levels of Kubernetes have you embedded in your Kubernetes yet? Would you like to share another Kubernetes-in-Kubernetes service with the community? Get in touch with us, and see you next week for another edition of VSHN.timer.
PS: would you like to receive VSHN.timer every Monday in your inbox? Sign up for our weekly VSHN.timer newsletter.
PS2: do you prefer reading VSHN.timer in your favorite RSS reader? Subscribe to this feed.
PS3: check out our previous VSHN.timer editions about Kubernetes: #4, #8, #11, #14, #16, #19, #23, #37, #46, #49, #59, #64, #74, #82, #97, #99, and #102.