[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-kubernetes-1-36-1-patch-releases-zh":3,"article-related-kubernetes-1-36-1-patch-releases-zh":32,"series-industry-3feb696c-9366-408a-b865-9110348ff03a":84},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":24,"views":28,"created_at":29,"published_at":30,"topic_cluster_id":31},"3feb696c-9366-408a-b865-9110348ff03a","kubernetes-1-36-1-patch-releases-zh","Kubernetes 1.36.1 與多條分支補丁更新","\u003Cp data-speakable=\"summary\">Kubernetes 釋出 v1.36.1，並同步更新 1.35、1.34、1.33 分支，重點是維持支援版本的補丁節奏。\u003C\u002Fp>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\" target=\"_blank\" rel=\"noopener\">Kubernetes\u003C\u002Fa> 在 5 月 12 日丟出一批新版本。主角是 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\u002Ftag\u002Fv1.36.1\" target=\"_blank\" rel=\"noopener\">v1.36.1\u003C\u002Fa>。同批還有 1.35、1.34、1.33 的補丁版。這種更新很樸素，但很重要。\u003Ca href=\"\u002Fnews\u002Fkubernetes-turns-clusters-into-declared-state-zh\">叢集\u003C\u002Fa>要穩，靠的就是這種例行維護。\u003C\u002Fp>\u003Cp>這次 \u003Ca href=\"\u002Ftag\u002Fgithub\">GitHub\u003C\u002Fa> release 頁面沒有長篇故事。它更像一張公告牌。官方把讀者導去 \u003Ca href=\"https:\u002F\u002Fgroups.google.com\u002Fg\u002Fkubernetes-announce\" target=\"_blank\" rel=\"noopener\">kubernetes-announce\u003C\u002Fa> 和 changelog。講白了就是，版本號先給你，細節自己去查。對 Kubernetes 這種跨平台、跨部署方式的專案，這種做法很合理。\u003C\u002Fp>\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Release\u003C\u002Fth>\u003Cth>Date\u003C\u002Fth>\u003Cth>Type\u003C\u002Fth>\u003Cth>GitHub reactions\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>v1.36.1\u003C\u002Ftd>\u003Ctd>May 12, 16:39\u003C\u002Ftd>\u003Ctd>Patch\u003C\u002Ftd>\u003Ctd>18\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>v1.35.5\u003C\u002Ftd>\u003Ctd>May 12, 15:37\u003C\u002Ftd>\u003Ctd>Patch\u003C\u002Ftd>\u003Ctd>6\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>v1.34.8\u003C\u002Ftd>\u003Ctd>May 12, 15:35\u003C\u002Ftd>\u003Ctd>Patch\u003C\u002Ftd>\u003Ctd>1\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>v1.33.12\u003C\u002Ftd>\u003Ctd>May 12, 14:09\u003C\u002Ftd>\u003Ctd>Patch\u003C\u002Ftd>\u003Ctd>8\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>v1.36.0\u003C\u002Ftd>\u003Ctd>Apr 22, 17:57\u003C\u002Ftd>\u003Ctd>Minor release\u003C\u002Ftd>\u003Ctd>74\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch2>這批更新到底在做什麼\u003C\u002Fh2>\u003Cp>這次最醒目的就是 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\u002Ftag\u002Fv1.36.1\" target=\"_blank\" rel=\"noopener\">Kubernetes v1.36.1\u003C\u002Fa>。另外還有 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\u002Ftag\u002Fv1.35.5\" target=\"_blank\" rel=\"noopener\">v1.35.5\u003C\u002Fa>、\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\u002Ftag\u002Fv1.34.8\" target=\"_blank\" rel=\"noopener\">v1.34.8\u003C\u002Fa>、\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\u002Ftag\u002Fv1.33.12\" target=\"_blank\" rel=\"noopener\">v1.33.12\u003C\u002Fa>。四個版本都在同一天\u003Ca href=\"\u002Fnews\u002Fvibe-coding-turns-app-ideas-into-crowded-markets-zh\">上線\u003C\u002Fa>，而且時間只差幾個小時。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1779198247447-a1ms.png\" alt=\"Kubernetes 1.36.1 與多條分支補丁更新\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>這種節奏對營運團隊很有感。很多公司不是只跑一個版本。常見情況是，主叢集在新版本，邊緣環境或舊客戶還卡在前一版。補丁同步發佈，代表你可以分批修，不用每次都硬切大版本。\u003C\u002Fp>\u003Cp>如果你有在管生產環境，這種 release 才是日常。不是每次都會有新功能可以吹。更多時候，真正值錢的是少一個 bug，少一次停機，少一個凌晨兩點的 alert。\u003C\u002Fp>\u003Cul>\u003Cli>v1.36.1 在 5 月 12 日 16:39 發佈\u003C\u002Fli>\u003Cli>v1.35.5 在 15:37 發佈\u003C\u002Fli>\u003Cli>v1.34.8 在 15:35 發佈\u003C\u002Fli>\u003Cli>v1.33.12 在 14:09 發佈\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>為什麼 release 頁面這麼簡短\u003C\u002Fh2>\u003Cp>Kubernetes 的 release notes 一直都不愛講廢話。GitHub 頁面只放最基本資訊。真正的變更細節，通常要去 changelog 看。這讓頁面看起來很冷靜，也很工程師。你要的是版本資訊，不是公關稿。\u003C\u002Fp>\u003Cp>這種寫法也有代價。對剛接觸 Kubernetes 的人來說，release 頁面幾乎像謎語。你知道有新版本，但不知道它修了\u003Ca href=\"\u002Fnews\u002Fwhy-claude-release-timeline-proves-platform-war-zh\">什麼\u003C\u002Fa>。要判斷要不要升級，還是得回頭查 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Fblob\u002Fmaster\u002FCHANGELOG\u002FCHANGELOG-1.36.md\" target=\"_blank\" rel=\"noopener\">Kubernetes changelog\u003C\u002Fa>。\u003C\u002Fp>\u003Cp>我覺得這很符合開源專案的現實。Kubernetes 不是單一 SaaS。它是很多公司一起維護的基礎設施專案。公告要短，文件要準，版本要穩。這三件事缺一個，整個社群就會開始痛苦。\u003C\u002Fp>\u003Cblockquote>“The Kubernetes project is built by dozens of companies and hundreds of individual contributors.” — \u003Ca href=\"https:\u002F\u002Fwww.cncf.io\u002Fblog\u002F2018\u002F03\u002F30\u002Fkubernetes-is-built-by-dozens-of-companies-and-hundreds-of-individual-contributors\u002F\" target=\"_blank\" rel=\"noopener\">Dan Kohn, CNCF\u003C\u002Fa>\u003C\u002Fblockquote>\u003Cp>這句話到現在還很貼切。Kubernetes 的更新不是某一家廠商拍腦袋就能做完。它是協作結果。你在 GitHub 上看到的每一個 patch，背後都是一堆人一起對齊、測試、簽核。\u003C\u002Fp>\u003Cp>所以別把這種 release 當成小事。對雲端平台來說，穩定補丁比華麗功能更實際。尤其是跑在 production 的 cluster，少一個安全修補或相容性修正，後面就是一串麻煩。\u003C\u002Fp>\u003Ch2>這批版本怎麼比\u003C\u002Fh2>\u003Cp>從數字看，最新的 minor line 最受關注。\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\u002Ftag\u002Fv1.36.0\" target=\"_blank\" rel=\"noopener\">v1.36.0\u003C\u002Fa> 有 74 個 reactions，明顯比 patch 版高很多。這很正常。新 minor release 通常會吸引更多人點進去看。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1779198247546-bccm.png\" alt=\"Kubernetes 1.36.1 與多條分支補丁更新\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>但 patch 版也不是沒人理。\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\u002Ftag\u002Fv1.36.1\" target=\"_blank\" rel=\"noopener\">v1.36.1\u003C\u002Fa> 還是拿到 18 個 reactions。\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\u002Ftag\u002Fv1.33.12\" target=\"_blank\" rel=\"noopener\">v1.33.12\u003C\u002Fa> 也有 8 個。這表示舊支援線還有實際使用者，不是發完就放生。\u003C\u002Fp>\u003Cp>對維運團隊來說，這裡的重點不是 reaction 數字本身，而是支援面。你如果還在 1.33、1.34、1.35，代表你有一條自己的升級路線。patch release 就是讓你可以慢慢走，不用一次搬整座山。\u003C\u002Fp>\u003Cul>\u003Cli>v1.36.0：74 reactions，熱度最高\u003C\u002Fli>\u003Cli>v1.36.1：18 reactions，最新補丁仍有關注\u003C\u002Fli>\u003Cli>v1.35.5：6 reactions，支援線還在動\u003C\u002Fli>\u003Cli>v1.34.8：1 reaction，低調但仍有更新\u003C\u002Fli>\u003Cli>v1.33.12：8 reactions，老版本還沒被丟掉\u003C\u002Fli>\u003C\u002Ful>\u003Cp>如果你把 Kubernetes 跟其他平台比，差異很明顯。很多商用平台只照顧少數版本。Kubernetes 這邊則是多條分支一起維護。這很累，但也很符合大型基礎設施的現實。\u003C\u002Fp>\u003Cp>另外，GitHub 還能看到前一版的 release candidate，像 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\u002Ftag\u002Fv1.36.0-rc.1\" target=\"_blank\" rel=\"noopener\">v1.36.0-rc.1\u003C\u002Fa> 和 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases\u002Ftag\u002Fv1.36.0-rc.0\" target=\"_blank\" rel=\"noopener\">v1.36.0-rc.0\u003C\u002Fa>。這代表正式版前，還是走完了完整的測試流程，不是隨便打包就丟上來。\u003C\u002Fp>\u003Ch2>對台灣團隊有什麼影響\u003C\u002Fh2>\u003Cp>如果你在台灣管雲端服務，這種 release 你應該要盯。不是因為它很熱鬧，而是因為它很實際。Kubernetes 的 patch release 常常牽涉到安全修補、相容性調整，還有一些你平常不會注意，但出事就很痛的細節。\u003C\u002Fp>\u003Cp>很多團隊會把升版排在固定維護窗。這很合理。問題是，有些人只看 minor version，忘了 patch 版。結果就是，叢集明明在支援範圍內，卻一直沒吃到修正。這種做法我真的不推，因為最後常常是事故來教你做人。\u003C\u002Fp>\u003Cp>比較務實的做法，是先看自己的版本矩陣，再對照 changelog。先確認控制平面、node pool、CNI、Ingress controller、CSI driver 這幾塊有沒有相依風險。升級不是按一顆按鈕。它是整串軟體一起動。\u003C\u002Fp>\u003Ch2>你現在該做什麼\u003C\u002Fh2>\u003Cp>如果你的叢集還在 1.33、1.34 或 1.35，先別急著衝。先查你用的雲端供應商版本支援表，再看對應 patch 的 changelog。把風險列出來，比盲升版更省時間。\u003C\u002Fp>\u003Cp>我的建議很簡單。把 patch release 當成例行維護，不要等到事故才看。你可以先在 staging 跑一次，再觀察 node、\u003Ca href=\"\u002Ftag\u002Fapi\">API\u003C\u002Fa> server、controller manager 的狀態。這種事沒什麼浪漫，但很有效。\u003C\u002Fp>\u003Cp>說到底，Kubernetes 這次的更新沒有花俏戲碼。它做的事很基本：讓支援中的版本繼續能用，讓維運團隊有空間安排升級。接下來你要做的，就是檢查自己的版本，別把補丁當空氣。\u003C\u002Fp>","Kubernetes 釋出 v1.36.1，並同步更新 1.35、1.34、1.33 分支。這次重點是維持支援版本的補丁節奏，方便叢集按計畫升級。","github.com","https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkubernetes\u002Freleases",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1779198247447-a1ms.png","industry","zh","99ed935d-9d44-41fa-b187-d4da05a927eb",[17,18,19,20,21,22,23],"Kubernetes","Kubernetes 1.36.1","patch release","Kubernetes release","雲端原生","叢集維運","GitHub release",[25,26,27],"Kubernetes 1.36.1 與 1.35、1.34、1.33 的補丁版同日發佈。","release 頁面很短，真正細節要看 changelog。","對維運團隊來說，這類補丁更新比新功能更實用。",3,"2026-05-19T13:43:37.638388+00:00","2026-05-19T13:43:37.226+00:00","caa87b65-9bbc-46fe-bba8-4f4158dd2d8b",{"tags":33,"relatedLang":43,"relatedPosts":47},[34,35,37,39,41],{"name":21,"slug":21},{"name":20,"slug":36},"kubernetes-release",{"name":17,"slug":38},"kubernetes",{"name":18,"slug":40},"kubernetes-1361",{"name":19,"slug":42},"patch-release",{"id":15,"slug":44,"title":45,"language":46},"kubernetes-1-36-1-patch-releases-en","Kubernetes 1.36.1 lands with fresh patch releases","en",[48,54,60,66,72,78],{"id":49,"slug":50,"title":51,"cover_image":52,"image_url":52,"created_at":53,"category":13},"b5d4728c-ee2a-4df6-93c2-42e814d51ea1","why-smci-rally-is-about-supply-not-just-ai-zh","為什麼 SMCI 的漲勢主要是供給故事，不只是 Agentic AI","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780529579886-q16r.png","2026-06-03T23:32:28.626882+00:00",{"id":55,"slug":56,"title":57,"cover_image":58,"image_url":58,"created_at":59,"category":13},"6321e31d-d862-4666-b105-cd24c26d6f5a","nvidia-huang-ai-boom-agent-demand-zh","黃仁勳：AI 代理需求撐起晶片行情","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780528669292-jtux.png","2026-06-03T23:17:26.844843+00:00",{"id":61,"slug":62,"title":63,"cover_image":64,"image_url":64,"created_at":65,"category":13},"c15e2bff-fceb-4990-bb15-197233a20c5c","arms-windows-on-arm-pitch-turns-into-a-playbook-zh","Arm 的 Windows on Arm 變成轉場模板","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780527800667-z8yc.png","2026-06-03T23:02:51.413117+00:00",{"id":67,"slug":68,"title":69,"cover_image":70,"image_url":70,"created_at":71,"category":13},"944aacaa-7f1b-4a11-8390-768b2a89c607","anthropic-partner-network-enterprise-ready-zh","Anthropic 讓夥伴網路變企業級","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780524191103-89dy.png","2026-06-03T22:02:45.952347+00:00",{"id":73,"slug":74,"title":75,"cover_image":76,"image_url":76,"created_at":77,"category":13},"fc8eafb2-1d73-468c-a784-1279f4732ea2","7-build-2026-announcements-for-microsoft-watchers-zh","7 個 Build 2026 觀察重點","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780523288803-hs3b.png","2026-06-03T21:47:43.306492+00:00",{"id":79,"slug":80,"title":81,"cover_image":82,"image_url":82,"created_at":83,"category":13},"6d2568ba-f5d3-41b3-8111-9fe820613e84","why-microsoft-new-ai-models-break-openai-dependence-zh","為什麼微軟自建 AI 模型，才是擺脫 OpenAI 依賴的正確路線","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780522384832-8cbv.png","2026-06-03T21:32:24.837196+00:00",[85,90,95,100,105,110,115,120,125,130],{"id":86,"slug":87,"title":88,"created_at":89},"ee073da7-28b3-4752-a319-5a501459fb87","ai-in-2026-what-actually-matters-now-zh","2026 AI 真正重要的事","2026-03-26T07:09:12.008134+00:00",{"id":91,"slug":92,"title":93,"created_at":94},"83bd1795-8548-44c9-9a7e-de50a0923f71","trump-ai-framework-power-speech-state-preemption-zh","川普 AI 框架瞄準電力、言論與州權","2026-03-26T07:12:18.695466+00:00",{"id":96,"slug":97,"title":98,"created_at":99},"ea6be18b-c903-4e54-97b7-5f7447a612e0","nvidia-gtc-2026-big-ai-announcements-zh","NVIDIA GTC 2026 重點拆解","2026-03-26T07:14:26.62638+00:00",{"id":101,"slug":102,"title":103,"created_at":104},"4bcec76f-4c36-4daa-909f-54cd702f7c93","claude-users-spreading-out-and-getting-better-zh","Claude 用戶更分散，也更會用","2026-03-26T07:22:52.325888+00:00",{"id":106,"slug":107,"title":108,"created_at":109},"bd903b15-2473-4178-9789-b7557816e535","openclaw-raises-hard-question-for-ai-models-zh","OpenClaw 逼問 AI 模型價值","2026-03-26T07:24:54.707486+00:00",{"id":111,"slug":112,"title":113,"created_at":114},"eeac6b9e-ad9d-4831-8eec-8bba3f9bca6a","gap-google-gemini-checkout-fashion-search-zh","Gap 把結帳搬進 Gemini","2026-03-26T07:28:23.937768+00:00",{"id":116,"slug":117,"title":118,"created_at":119},"0740e53f-605d-4d57-8601-c10beb126f3c","google-pushes-gemini-transition-to-march-2026-zh","Google 把 Gemini 轉換延到 2026 年 3…","2026-03-26T07:30:12.825269+00:00",{"id":121,"slug":122,"title":123,"created_at":124},"e660d801-2421-4529-8fa9-86b82b066990","metas-llama-4-benchmark-scandal-gets-worse-zh","Meta Llama 4 分數風波又擴大","2026-03-26T07:34:21.156421+00:00",{"id":126,"slug":127,"title":128,"created_at":129},"183f9e7c-e143-40bb-a6d5-67ba84a3a8bc","accenture-mistral-ai-sovereign-enterprise-deal-zh","Accenture 攜手 Mistral AI 賣主權 AI","2026-03-26T07:38:14.818906+00:00",{"id":131,"slug":132,"title":133,"created_at":134},"191d9b1b-768a-478c-978c-dd7431a38149","mistral-ai-faces-its-hardest-year-yet-zh","Mistral AI 迎來最硬的一年","2026-03-26T07:40:23.716374+00:00"]