为什么说 Kubernetes 是一辆翻斗车
Kubernetes

> 
> 翻斗车是解决各种基本业务问题的优雅解决方案。
> 
> 
> 


![](/data/attachment/album/201906/24/012846v737bts00uwk3qd7.jpg)


这篇文章写于 Kubernetes 的生日（6 月 7 日星期五）前夕。


翻斗车很优雅。说真的，不信你听我说。它们以优雅的方式解决了各种各样的技术问题。它们可以搬动泥土、砾石、岩石、煤炭、建筑材料或道路上的障碍。它们甚至可以拉动拖车及它们上面的其他重型设备。你可以给一辆翻斗车装上五吨泥土，然后自驾游遍全国。对于像我这样的电脑极客来说，那就是优雅。


但是，它们并不容易使用。驾驶翻斗车需要特殊的驾驶执照。它们也不容易装配和维护。购买翻斗车和各种维护时要做很多选择。但是，它们可以优雅的搬动那些垃圾。


你知道搬动垃圾有什么不优雅的地方吗？假如你有一款新型的紧凑型轿车，它们到处可以买到，易于驾驶、更易于维护。但是，用它们来装泥土就很糟糕。这需要跑 200 趟才能运走 5 吨垃圾，而且，之后没人再会想要这辆车了。


好吧，你可以买一辆出售的翻斗车，而不是想自己造一辆。但是我不同，我是个极客，我喜欢自己造东西。但……


如果你拥有一家建筑公司，你就不会想着自己造一辆翻斗车。你肯定不会维持一条供应链来重构翻斗车（这可是一条很大的供应链）。但你可以学会驾驶一辆。


好吧，我的这个比喻很粗糙，但很容易理解。易用性是相对的，易于维护是相对的，易于装配也是相对的。这实际上取决于你想要做什么。[Kubernetes](https://kubernetes.io/) 也不例外。


一次性构建 Kubernetes 并不太难。配置好 Kubernetes 呢？好吧，这稍微难一些。你如何看待 KubeCon？它们又宣布了多少新项目？哪些是“真实的”呢？而你应该学习哪些？你对 Harbour、TikV、NATD、Vitess，开放策略代理有多深入的了解？更不用说 Envoy、eBPF 和 Linux 中的一系列底层技术？这就像是 1904 年工业革命爆发时建造翻斗车一样，你要弄清楚使用的螺钉、螺栓、金属和活塞。（有没有蒸汽朋克在这里吗？）


像翻斗车一样构造和配置 Kubernetes 是一个技术问题，如果你从事金融服务、零售、生物研究、食品服务等等，这可能不是你应该做的事情。但是，学习如何驾驶 Kubernetes 肯定是你应该学习的东西。


Kubernetes 就像一辆翻斗车，因其可以解决的各种技术问题（以及它所拖带的生态系统）而优雅。所以，我会给你一句引用的话，这是我的一位计算机科学教授在我大学的第一年告诉我们的，她说，“有一天，你会看到一段代码并对自己说，‘真特么优雅！’”


Kubernetes 很优雅。




---


via: <https://opensource.com/article/19/6/kubernetes-dump-truck>


作者：[Scott McCarty](https://opensource.com/users/fatherlinux) 选题：[lujun9972](https://github.com/lujun9972) 译者：[wxy](https://github.com/wxy) 校对：[wxy](https://github.com/wxy)


本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出


OK
As we approach Kubernetes anniversary on Friday, June 7 this week let's start with this.

Dump trucks are elegant. Seriously, stay with me for a minute. They solve a wide array of technical problems in an elegant way. They can move dirt, gravel, rocks, coal, construction material, or road barricades. They can even pull trailers with other pieces of heavy equipment on them. You can load a dump truck with five tons of dirt and drive across the country with it. For a nerd like me, that's elegance.

But, they're not easy to use. Dump trucks require a special driver's license. They're also not easy to equip or maintain. There are a ton of options when you buy a dump truck and a lot of maintenance. But, they're elegant for moving dirt.

You know what's not elegant for moving dirt? A late-model, compact sedan. They're way easier to buy. Easier to drive. Easier to maintain. But, they're terrible at carrying dirt. It would take 200 trips to carry five tons of dirt, and nobody would want the car after that.

Alright, you're sold on using a dump truck, but you want to build it yourself. I get it. I'm a nerd and I love building things. But…

If you owned a construction company, you wouldn't build your own dump trucks. You definitely wouldn't maintain the supply chain to rebuild dump trucks (that's a big supply chain). But you would learn to drive one.


OK, my analogy is crude but easy to understand. Ease of use is relative. Ease of maintenance is relative. Ease of configuration is relative. It really depends on what you are trying to do. [Kubernetes](https://kubernetes.io/) is no different.

Building Kubernetes once isn't too hard. Equipping Kubernetes? Well, that gets harder. What did you think of KubeCon? How many new projects were announced? Which ones are "real"? Which ones should you learn? How deeply do you understand Harbor, TikV, NATD, Vitess, Open Policy Agent? Not to mention Envoy, eBPF, and a bunch of the underlying technologies in Linux? It feels a lot like building dump trucks in 1904 with the industrial revolution in full swing. Figuring out what screws, bolts, metal, and pistons to use. (Steampunk, anyone?)

Building and equipping Kubernetes, like a dump truck, is a technical problem you probably shouldn't be tackling if you are in financial services, retail, biological research, food services, and so forth. But, learning how to drive Kubernetes is definitely something you should be learning.

Kubernetes, like a dump truck, is elegant for the wide variety of technical problems it can solve (and the ecosystem it drags along). So, I'll leave you with a quote that one of my computer science professors told us in my first year of college. She said, "one day, you will look at a piece of code and say to yourself, 'now that's elegant!'"

Kubernetes is elegant.

## Comments are closed.