VSHN.timer #4: The Sound Of Inevitability

Welcome to the new VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system and making us think, laugh, or simply work better.

This week we feature a few articles stating what is in everyone’s mind: Kubernetes is becoming the new standard platform for cloud applications.

1. The Register published an interesting interview with Pivotal’s CEO about the „inevitability“ of Kubernetes. It is an interesting article, with both positive and negative points, highlighting gains and pains in equal measure. Adopting K8s requires a substantial investment of time and money, something many companies jumping on the „cloud“ hype wagon do not always take into account. In any case, the word „inevitability“ brings both Thanos and Agent Smith to our minds, and we just hope nobody will snap the fingers of the Infinity Gauntlet right in the middle of that deployment into production. Just look at the stock price that appears at the end of that article to see what we mean.

https://www.theregister.co.uk/2019/07/29/pivotal_ceo_interview/

2. The pain points can be many, and not all teams are ready to handle them properly; this is not a fault of those teams, but most often a cause of the relative youth of the ecosystem. Case in point: Grafana’s own account of how badly configured pod priorities caused a production outage. K8s is fun and exciting and has lots of promise, but as an industry we are all still learning from mistakes, and this is a natural process. Thankfully the Grafana team could restore the systems after only 26 minutes and without any data loss – their story is a remarkable one and absolutely worth a read.

https://grafana.com/blog/2019/07/24/how-a-production-outage-was-caused-using-kubernetes-pod-priorities/

3. According to David Carboni, the prize of inevitability is invisibility. Well, actually David said „ubiquity,“ and we hope he does not mind us shortening the lexical distance between those two words. In the tag cloud generated by heated debates, there is one major thing everybody seems to agree about K8s: declarative state is the way to go. Describe how your system should look like, and let the machine decide how to implement it in the best possible way. And those YAML files are enabling a depth of communication between architects, developers and operation teams like we have not seen before. And this, in turn, will make K8s just another POSIX.

https://levelup.gitconnected.com/why-kubernetes-will-disappear-10ffcfb39f01

4. And what a platform K8s has become. If you have any doubts, just check this review of Kubernetes tools by Ellen Körbes from Garden.io. An amazing compilation with lots of cool new shiny toys to install and run and try and test. We do not know about you, but we are certainly testing them right now.

https://garden.slides.com/ellenkorbes/k8sdevtools?token=t3egVfZS#/

5. To complete the list above, here is a cool new tool we have recently discovered: Monday, a CLI executable (written in Go, duh!) that creates a hybrid local/remote configuration for applications written in several programming languages, enabling us to run part of our clusters locally and the other parts remotely. Really cool!

https://github.com/eko/monday

Do you have any cool links to share with us? What do you think about Kubernetes becoming the next POSIX? Do you think it is inevitable? Let us know in the comments below, and see you next week for another edition of VSHN.timer.