导致Kubernetes难用的四大因素

{"type":"doc","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Kubernetes为何如此难用?本文给出了4个原因,并指出了如何做才能使其易于使用。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"介绍"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Kubernetes(k8s)在过去几年曾经风靡一时,因为对于运行容器的生产工作负载来说,应用程序编排已经成为事实上的牌局需求。“容器化”应用程序相对简单,大多数称职的DevOps工程师都能创建一些Dockerfile,并都能在准备运行的管道中构建镜像。但是你在哪里“运行”你的Docker容器呢?你要部署哪些版本呢?所有的容器是如何相互通信的呢?这就是编排发挥作用的地方,也是大型供应商提供某些选项的地方。在撰写本文时,有两个主要的选项可用:来自Amazon Web Services(AWS)的弹性容器服务(Elastic Container Service,ECS)及所有基础设施即服务(IaaS)提供商(甚至包括AWS)提供的Kubernetes。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"编排的希望在于:能够使公司快速、轻松地将其容器化的应用程序交付到测试和集成环境中。理想的情况是“就是这么好用”( “ it just works”),也就是说,在看到应用程序在你面前运行之前,你只需要放松下手指并等待几分钟。理想情况下,你只需要指定运行应用程序所需的最少信息(名称、框架、依赖项等等,但这些最好也是从现有的可用配置文件中读取)即可。这就是编排希望的全部。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"显然,从标题上看,我们关注的是Kubernetes,主要是因为它是无处不在的,唯一例外的其他选项就是ECS,但这也正好证明了我们论文的观点:Kubernetes很难使用,因为AWS提出了自己的解决方案,并且更易于使用。但是为什么Kubernetes这么难用呢?用K8s运行应用程序需要多长时间?为什么它不易于使用呢?"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"Kubernetes的基础设置很难用"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"即使大多数公司不会自己构建自己的Kubernetes集群,我们也要从基础设施开始。如果你打算使用托管基础设施服务,那么K8s将是首选。我敢肯定有些人会在自己笔记本电脑上启动"},{"type":"link","attrs":{"href":"https:\/\/minikube.sigs.k8s.io\/docs\/start\/?fileGuid=qHW6vpwdxtX9Qgxv","title":"","type":null},"content":[{"type":"text","text":"minikube"}]},{"type":"text","text":",然后对自己说,“哇,这太简单了!我可以自己做!!”这让我想起了那些在笔记本电脑上启动"},{"type":"link","attrs":{"href":"https:\/\/www.elastic.co\/guide\/en\/elastic-stack-get-started\/current\/get-started-elastic-stack.html?fileGuid=qHW6vpwdxtX9Qgxv","title":"","type":null},"content":[{"type":"text","text":"Elasticsearch"}]},{"type":"text","text":"容器的人,他们会说,“哇,我们应该在我们的网站实现这个!!”。快进到六个月或一年后的产品发布,简单的“我们自己能做到”的口号变成了“我希望我们不必再这样做了。”"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"如果你真的要构建自己的Kubernetes集群,那么你需要通过所选择的IaaS在你的裸机或虚拟机(VM)上构建所有的控制平面(control plane)服务器和服务,然后使用一些奇特的网络配置将它们连接在一起,以将控制平面流量与容器流量分开。你需要配置和运行所有的控制平面软件,并让它们相互通信,稳定运行并进行适当的监控。有悖常理的是,你需要编排用于编排应用程序的容器,但又无需进行大量的编排!当你在Windows上运行minikube或Docker Desktop时,你会看到一个奇妙的幻影,它隐藏了所有使用容器运行容器编排系统的初始状态。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"我们甚至还没有谈到Ingress(通常就是nginx实例)和位于控制平面堆栈顶部或旁边的负载平衡器的复杂性。很多时候,你会觉得自己在创建一个完整的基础设施,只是为了让你的基础设施运行(这并不罕见,但肯定不会比你自己尝试编排更好)。我们还没有深入了解基于角色的身份验证控制(Role Based Authentication Controls)和网络策略,这些需要设置成能支持在一个集群中运行的多个应用程序或堆栈。配置点和服务器端设置的数量开始迅速增加,我们甚至还没有开始编排应用程序,这才是我们创建编排系统的意义所在。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"让我们假设你确实踏入到了波涛汹涌冰冷刺骨的北大西洋深处,并为自己建造了一艘具有生产价值的船只,可以将你的容器编排成一个实际的应用程序。你回过头来看下日历,从你开始到现在已经过去了六个月或者一年,你现在正在部署一个控制平面,上面写着“你好,世界!”(“Hello World!”)你认为自己成功了,正要庆祝一下,但查看网站上的发布板块时,却发现你又有一个新版的k8s要部署!!!"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"我听到你们在说什么了,“我们是一家大公司,我们有很多DevOps工程师,他们是全世界最顶尖的工程人才。我们能够应付所有这些繁重的工作。你只是个爱发牢骚、爱嫉妒的孩子。”我看到你了,"},{"type":"link","attrs":{"href":"https:\/\/www.youtube.com\/watch?v=HDm9iNkLyPI&fileGuid=qHW6vpwdxtX9Qgxv","title":"","type":null},"content":[{"type":"text","text":"Datadog"}]},{"type":"text","text":"和"},{"type":"link","attrs":{"href":"https:\/\/www.youtube.com\/watch?v=wqXVKneP0Hg&fileGuid=qHW6vpwdxtX9Qgxv","title":"","type":null},"content":[{"type":"text","text":"Ticketmaster"}]},{"type":"text","text":"。(顺便说一句,你对嫉妒的指责可能是对的。在我的好朋友Justin Dean的主题演讲结束时,他展示了所有团队成员的幻灯片,我的照片应该在上面——但我两年前就离开了团队。)对于其他所有人来说,我们一致决定不花六个月或一年的时间来构建自己的控制平面,只是启动我们IaaS供应商的托管服务,然后祈祷就好了。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"k8s的YAML不是标记语言"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"如果你已经跳过了前面的内容,并且刚刚启动了一个托管的k8s集群,你仍需经历一段漫长而乏味的旅程,会陷入YAML这个令人困惑的深渊。YAML之于文本就像詹姆斯·乔伊斯(James Joyce)的"},{"type":"link","attrs":{"href":"https:\/\/www.finwake.com\/1024chapter1\/fw01.htm?fileGuid=qHW6vpwdxtX9Qgxv","title":"","type":null},"content":[{"type":"text","text":"《芬尼根的守灵》(Finnegan’s Wake)"}]},{"type":"text","text":"之于英语一样。如果你闭上一只眼,只用左手的小拇指和右手的大拇指跟随几个巴西音,把你的脚放在芭蕾舞的第五个姿势,然后再低声背诵二战密码,那么你就会很容易看出YAML是相当容易理解的了。一旦你掌握了它的窍门,就像骑自行车在一个冰冻的湖面上,虽然冰只有厘米厚,但狂野的狼在追你。这就像闯入了黄金大劫案时期在诺克斯堡(Fort Knox)举行的远古外星人(Ancient Aliens)鸡尾酒会一样简单。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"看,实际上并不难,对吧?假设有一个人在街上向你走来。他是一位k8s专家,他将要向你展示部署“你好,世界!”这个Web服务是多么简单。对话是这样的:"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"codeblock","attrs":{"lang":"plain"},"content":[{"type":"text","text":"Him: “kind: Deployment”\nYou: “Oh, I see. Yes, I like it.”\nHim: “apiVersion: apps\/v1beta1.”\nYou: “Uh, okay. Isn’t v1beta1 out of date? You can use v1 as of k8s 1.9.\nIt’s actually removed in 1.16, but I wonder how many people have never\nupdated.”\nHim: “Start over.”\nYou: “Wat.”\nHim: “kind: Deployment”\nYou: “Stop with the Kinds everywhere!”\nHim: “apiVersion: apps\/v1”\nYou: “This again.”\nHim: “spec:”\nYou: “Huh??”\nHim: “selector:”\nYou: “No.”\nHim: “matchLabels:”\nYou: “Wat.”\nHim: “app: nginx”\nYou: “That’s nearly the first thing I’ve understood about this so far.”\nHim: “spec:”\nYou: “Again?”\nHim: “containers:”\nYou: “Okay, now we’re getting somewhere.”\nHim: “image: nginx:1.14.2”\nYou: “Hmm.”\nHim: “ports:”\nYou: “Aiiiiieeee.”\nHim: “containerPort: 80”\nYou: “I’m going home. I quit. There must be a devops job I can get where\nI work on [Gatsby blogs](https:\/\/www.gatsbyjs.com\/ \"Gatsby nodejs frontend\")\nall day.”\n"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"这只是试着去阅读和理解文件。尝试阅读两个k8s yaml示例,然后从头开始自己编写一个。更好的方法是,每天都尝试一种CodeKata实践,编写可运行可部署的Kubernetes配置。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"复制粘贴不是代码"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"我还在为上一节的内容而暗自发笑,因为这是我每天生活中的日常痛苦点,而直面这种痛苦就像是站在高速公路上Keanu Reeves驾驶的公共汽车面前一样。唯一能让我继续埋头苦干的是我意识到使用NodeJs会更糟。问题在于Kubernetes的文档相当好。你复制粘贴一些“你好,世界!”的示例,输出看起来就可以工作。你开始很擅长使用kubectl了。你可以在YAML中看到模糊的形状和轮廓。你开始有了信心,相信自己也许能做一些有用的事情。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"“让我们尝试将应用程序迁移到Kubernetes!“当你全身湿淋淋地从浴缸里出来、只裹着一条毛巾时,你大喊大叫,就像"},{"type":"link","attrs":{"href":"https:\/\/www.scientificamerican.com\/article\/fact-or-fiction-archimede\/?fileGuid=qHW6vpwdxtX9Qgxv","title":"","type":null},"content":[{"type":"text","text":"阿基米德(Archimedes)"}]},{"type":"text","text":"在雪城(Syracuse)的街道上奔跑一样。“我们只需在这里复制一些片段,然后粘贴到那里,就可以立即运行我们的应用程序了,”你屏息向同事解释。“行吗?!“他们兴奋地问。“还不行。我是说,还需要缩进下这个片段,删除一个在这个规范中没有使用的片段。然后需要决定是使用部署(deployment)或守护程序(daemonset),但它肯定能行的。我发誓!”"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"首先,穿上衣服。我完全赞成一边洗澡一边思考kubernetes YAML文件,但你需要先穿好衣服。另外,我知道如果你把Macbook Air丢进浴缸,结果可能会更另让人激动。其次,这里有一个谜团:你认为运行和部署应用程序需要多少个YAML文件?幸好人有十个手指和十个脚趾,这是件好事,因为这可能就是你需要的数量。它们都是相关的,但又并没有真正的关联。如果你喜欢冒险且容易上当受骗,你可以复制粘贴这些片段,但是你不知道这些片段是否兼容。只有四个必填字段,但都是乱码,所有内容都在"},{"type":"codeinline","content":[{"type":"text","text":"spec:"}]},{"type":"text","text":"(包括"},{"type":"codeinline","content":[{"type":"text","text":"spec:"}]},{"type":"text","text":")下。大部分都是重复的,但都又只重复一点。它们在宏观上是相同的部分在微观上其实是不同的。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"复制粘贴是一门很棒的艺术,我个人的整个职业生涯都是这样。我很高兴地承认,我生活中的所有产出就像是从stack overflow和文档示例中剪下的"},{"type":"link","attrs":{"href":"https:\/\/tvtropes.org\/pmwiki\/pmwiki.php\/Main\/CutAndPasteNote?fileGuid=qHW6vpwdxtX9Qgxv","title":"","type":null},"content":[{"type":"text","text":"勒索信(ransom note)"}]},{"type":"text","text":"。但是,通过拼凑这张脆弱的文本网来做实际上本该很简单且明显的事情是乏味且容易出错的,而且这也是被反复验证的结果。更好的方法是表达你想要什么,并且能够实际地发出可操作的、可执行的代码来产生你想要的结果:即应用程序运行。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"所有关于YAML的抱怨都很有趣,但实际上这也是原因的征兆:Kubernetes如此难用,因为接口必须是完全刚性的。K8s的配置不是活生生的、雄伟的树木,而是一堆枯木。它们比砍掉的木头还要糟糕,它们是整片石化的森林,巨大的岩石堆,上面印着几千年的年轮,已经被保存了数百万年。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"不,它们比石化的森林还糟糕!Kubernetes所展示的是二十一世纪的打孔卡片。每一个YAML都是一个孔的集合,这些孔被戳进我们无法阅读和理解的碎木卡中,我们盲目地将这些孔塞进"},{"type":"codeinline","content":[{"type":"text","text":"kubectl apply-f"}]},{"type":"text","text":"命令中,并且我们希望能以正确的顺序放置它们,在堆栈中的任何地方都没有放错孔。然后,就像过去的机器一样,我们试图通过观察闪烁的灯光和模糊的录音带输出来了解正在发生的事情,并希望能够收集到一些信息。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"就像尝试在"},{"type":"link","attrs":{"href":"https:\/\/en.wikipedia.org\/wiki\/Player_piano#Music_rolls?fileGuid=qHW6vpwdxtX9Qgxv","title":"","type":null},"content":[{"type":"text","text":"自动钢琴"}]},{"type":"text","text":"上重现莫扎特(Mozart)或贝多芬(Beethoven)的音乐一样,是一件乏味、费力、容易出错并且最终无法实现的事情,同样,k8s的表现形式也会被永久冻结,无法表达性地写出来,而且会无限地演奏同一首曲子。尽管v1已经推出两年了,但人们仍然使用v1beta1,原因是从那时起就没有人再生成新的k8s配置了。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"很难调试"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"k8s最棒的地方在于:当出现问题时,没人知道。我已经数不清有多少次我部署了一些东西,然后投入到其他事情中去了,几个小时后回来,发现部署悄然失败了,没有人通知我。只有几个地方的错误信息是可用的:部署日志中的还是在pod日志中?ingress或ingress部署是否还在运行?在数十个Kind文件中,日志条目会出现在哪里?根本原因通常是一些不相关的问题:一个错误的、看不见的空格;应该用双引号但没有用;应该用单引号也没有用;或者三周前在修复复制-粘贴问题时,缩进被破坏了。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"当然,有一些工具、技术和监控工具可以帮助我们解决这个问题;这就像埃隆·马斯克(Elon Musk)的"},{"type":"link","attrs":{"href":"https:\/\/youtu.be\/aBr2kKAHN6M?t=837&fileGuid=qHW6vpwdxtX9Qgxv","title":"","type":null},"content":[{"type":"text","text":"火星轨道飞行器MVP"}]},{"type":"text","text":":“这有用吗?“当然!!一千次,都是的!“它有什么用?“它几乎是你想要的任何东西!”你必须知道要找什么,在哪里找,然后必须知道如何找出解决方法,那么你就必须知道在这数十个文件中哪一行或哪几行需要修复,然后你也必须要知道如何修复它们。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"k8s的另一个优点是你拥有了它就拥有了一切。听着:朋友(friendo),伙计(pal),老兄(buddy),你选择了这种存在。你复制粘贴的“代码”。文档示例可以起作用。我可以在我的笔记本电脑上运行“你好,世界!”,很明显,这都是你的功劳。你就是那个穿着毛巾湿漉漉地跑过办公室喊“Kubernetes!”的人,如果希波克拉底誓言(Hippocratic oath)是“不要伤天害理”(“Do no harm” ),那么Devops的誓言可能就是“别做坏事,否则你将被解雇。”"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"而k8s最伟大之处在于:有很多人和公司声称他们知道发生了什么、该怎么办,他们会很乐意拿着你的钱来告诉你这是不是真的。在搜索引擎中输入Kubernetes,就可以看到所有弹出的广告。本文就是该问题的一部分,也是解决方案的一部分,所以请继续听下去。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"最后,解决方案"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"有几种方法可以使Kubernetes更易于使用:"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"numberedlist","attrs":{"start":1,"normalizeStart":1},"content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":1,"align":null,"origin":null},"content":[{"type":"text","text":"不要用k8s: run,尖叫着逃命吧"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":2,"align":null,"origin":null},"content":[{"type":"text","text":"训练所有的人都来解决这个问题(当你完成后再来找我;我可能还活着。也许已经不在了。)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":3,"align":null,"origin":null},"content":[{"type":"text","text":"为你的团队雇佣更多的人来解决这个问题(我有空,打电话给我。哈哈,开玩笑的。)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":4,"align":null,"origin":null},"content":[{"type":"text","text":"请别人帮你做"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":5,"align":null,"origin":null},"content":[{"type":"text","text":"等待更长的时间,少花钱多办事,最终选择做一些不可怕的事情"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":6,"align":null,"origin":null},"content":[{"type":"text","text":"寻找一种解决方案,将你的应用程序部署到适合你的环境中,然后继续进行你实际上从事的任何业务。自动化工具和服务可以帮助你运行应用程序,而无需对上述活动进行投资。总得有人去做,但最好不是你。"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"原文链接:"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/releasehub.com\/blog\/why-kubernetes-is-so-hard?fileGuid=qHW6vpwdxtX9Qgxv","title":"","type":null},"content":[{"type":"text","text":"https:\/\/releasehub.com\/blog\/why-kubernetes-is-so-hard"}]}]}]}
發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章