# 50 Reasons Kubernetes Sucks ###### tags: `Kubernetes` TC: fo-fitty To those that actually believe, really and truly believe this hype driven PoS with so many issues they had to distribute the parts because the sum of which would = failure. There is no honest person that can say k8s is a great platform. 那些真的相信，實實在在地相信這個炒作的PoS驅動有這麼多的問題，他們不得不分發零件，因為總和等於失敗。 沒有誠實的人可以說k8s是一個很好的平台。 Here are 50 reasons why it sucks, and will continue to suck forever, there is no saving this shite, may god have mercy on your souls for those that continue to hype this dribble. 這裡有50個原因，它會吸引人，並且將永遠持續吸引人，沒有任何保留的理由，也許上帝會對那些繼續炒作運球的人憐憫你的靈魂。 1) no one wants to manage a cloud inside a cloud 沒有人願意來管理雲中雲 2) breaking api changes 打破api的變化 3) breaking charts 打破圖表 4) node upgrades node 升級 5) cluster upgrades 叢集升級 6) cert management breakages 證書管理失敗 7) hard core folks become elitist all-in or nothing assholes 核心人員變成了精英主義者，全是或沒有混蛋 8) it makes your 🍆 shrink 它使您的🍆收縮 9) kubectl carpal tunnel kubectl腕管 10) private overlay networks are awful 專用覆蓋網絡很糟糕 11) service meshes are garbage on top of more garbage 服務網格是垃圾中的垃圾 12) no over provisioning of cpu or memory (mutha fucka, dont tell me how to run my OS) 沒有過度配置cpu或內存（mutha fucka，不要告訴我如何運行我的操作系統） 13) come back in 2 years and try and upgrade your shit 別想在2年左右回來嘗試升級 14) golang sucks golang很爛 15) api slows down over time due to too many events 由於事件太多，api會隨著時間的推移而變慢 16) people thinks its a good idea to have 50% of their compute account for k8s monitoring and metric overhead 人們認為將其計算帳戶的50％用於k8s監視和度量標准開銷是一個好主意 17) they just dumped Docker, assholes! 它不使用 docker 18) who wants all their company resources on this steaming pile of dung 誰想要他們所有公司的資源都是不好的 19) vms are making a comeback coz their easier to manage at scale now 虛擬機正在使捲土重來，因為它們現在更易於大規模管理 20) good luck having an outage when the nginx container is rate limited in a production env 21) oh my god, all the developer support required, no go RTFM for homegrown or bastardize cloud implementations 22) kube-proxy sucks 23) the kubelet can go bl*w goats 24) omg someone at google wrote the ingress controller, piece of shit that just primes nginx configs with rate limiting and fugly ass annotations, why oh why o lord have thou forsaken me! 25) golang templates and helm charts 26) helm v3 27) helmfile 28) helmsman 29) every single fucking Kubernetes SDK 30) Taints and Tolerations 31) crash loop backoffs 32) k8s “pause” containers 32) base64 encoded secrets 33) performance performance performance sucks 34) folks that want to host their companies shitty 35) web apps and apis in a ticking time bomb of the DevOps team with 1 college degree hire and 2 interns, and 1 senior guy that knows to keep his mouth shut or get whacked. 36) github issues trolling for X controller or Y package or Z whatever the fuck else 37) it gives you cancer of the anus 38) its the ultimate trojan horse deathtrap for burgeoning businesses, stay away if your solvent! 39) who really thinks anything that is capable of running “thousands” of nodes is a good idea? 40) why k8s folks wanna grab all the containers for themselves? 41) my OS scheduler works better 42) how fast do you really think service labels are? 43) how were we so stupid to fall into this trap? 44) so now I have a 1 year old setup that we spent 18 months building is now in a place that no one wants to touch and my entire new team wants to spend time building the next version - no this is not innovation dummies 45) did i mention that it shrinks 🍆, it also stretches 🍩 beyond usability save for extra storage volume 46) it smells like doodoo 47) who thought CRDS were a good idea 48) so we’re in prod but have beta apis? How does that work in the real world 49) my friends can launch a fleet of VMs in 1/10th of the time I can get a dev environment up and running 50) its the Antichrist of container orchestration 51) its shine has already faded, and the paint is peeling and the tires are dull