[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-5-kops-release-notes-for-kubernetes-admins-zh":3,"article-related-5-kops-release-notes-for-kubernetes-admins-zh":33,"series-industry-247a7941-89df-44fe-87d8-7e906dba45f3":86},{"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":25,"views":29,"created_at":30,"published_at":31,"topic_cluster_id":32},"247a7941-89df-44fe-87d8-7e906dba45f3","5-kops-release-notes-for-kubernetes-admins-zh","5 個 kOps 版本重點","\u003Cp data-speakable=\"summary\">這篇整理 5 個 kOps 版本重點，幫你判斷現在該升到哪版、哪些支援即將移除。\u003C\u002Fp>\u003Cp>如果你在管 kOps，讀完這 5 項就能判斷：現在該跟進哪個穩定版、哪些相容性要先補、以及下一次叢集升級要避開\u003Ca href=\"\u002Fnews\u002Fwhy-openai-is-right-to-push-back-on-white-house-ai-safety-ru-zh\">什麼\u003C\u002Fa>風險。頁面上的最新穩定版是 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkops\u002Freleases\u002Ftag\u002Fv1.35.1\">v1.35.1\u003C\u002Fa>，而且還有一個明確的下一步訊號。\u003C\u002Fp>\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>項目\u003C\u002Fth>\u003Cth>版本\u003C\u002Fth>\u003Cth>重點訊號\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>穩定版\u003C\u002Ftd>\u003Ctd>v1.35.1\u003C\u002Ftd>\u003Ctd>目前頁面最新標記\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>預發布版\u003C\u002Ftd>\u003Ctd>v1.36.0-alpha.1\u003C\u002Ftd>\u003Ctd>透露下一版移除項目\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>支援通知\u003C\u002Ftd>\u003Ctd>kOps 1.36\u003C\u002Ftd>\u003Ctd>將移除 Kubernetes 1.30 支援\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch2>1. 最新穩定版：v1.35.1\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkops\u002Freleases\u002Ftag\u002Fv1.35.1\">v1.35.1\u003C\u002Fa> 是這份版本頁面上標示為 Latest 的穩定版，代表它是目前最值得先看的正式發行版本。它不是單純補一個小號碼，而是把 \u003Ca href=\"\u002Ftag\u002Faws\">AWS\u003C\u002Fa>、GCE、Azure、Hetzner、Cilium、etcd-manager 與 kops-controller 路徑上的多個修補一起帶進來。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780586284483-09lo.png\" alt=\"5 個 kOps 版本重點\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>對維運人員來說，這類版本通常偏向修正與穩定，不是大改功能。你可以把它視為一次集中整理：叢集生命週期、網路行為、控制器流程、Go 與 containerd 版本更新，都在這個版本裡一起處理。\u003C\u002Fp>\u003Cul>\u003Cli>發布日期：5 月 28 日\u003C\u002Fli>\u003Cli>頁面標記：Latest\u003C\u002Fli>\u003Cli>提供 20 個主要平台資產\u003C\u002Fli>\u003Cli>含從 v1.35.0 到 v1.35.1 的完整變更紀錄\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>2. Kubernetes 1.30 支援即將退場\u003C\u002Fh2>\u003Cp>版本頁面摘要已經直接寫明：Kubernetes 1.30 的支援會在 kOps 1.36 移除。這是整份 release notes 裡最重要的前瞻訊號，因為它不是「可能」而是已經排進下一版的變更。\u003C\u002Fp>\u003Cp>如果你的叢集還跑在 Kubernetes 1.30，現在就該把它列成升級排程。最實際的做法，是先盤點每個叢集的控制平面版本，再安排測試升級路徑，避免等到 kOps 1.36 \u003Ca href=\"\u002Fnews\u002Fclaude-partner-network-learning-path-launches-zh\">上線\u003C\u002Fa>後才被動處理。\u003C\u002Fp>\u003Cul>\u003Cli>受影響版本：Kubernetes 1.30\u003C\u002Fli>\u003Cli>移除目標：kOps 1.36\u003C\u002Fli>\u003Cli>第一步：盤點所有叢集版本\u003C\u002Fli>\u003Cli>第二步：先驗證下一個 minor upgrade\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>3. v1.36.0-alpha.1 先告訴你未來會少什麼\u003C\u002Fh2>\u003Cp>預\u003Ca href=\"\u002Fnews\u002Fwhat-we-know-about-gpt-56-release-date-zh\">發布\u003C\u002Fa>版 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkops\u002Freleases\u002Ftag\u002Fv1.36.0-alpha.1\">v1.36.0-alpha.1\u003C\u002Fa> 的價值，不在於你現在要不要直接上 alpha，而在於它提前揭露下一條發行線的方向。這份 notes 裡可以看到一些移除與清理工作，例如 Amazon Linux 2 支援被拿掉，還有部分舊 mirror 參照被刪除。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780586278737-gaj5.png\" alt=\"5 個 kOps 版本重點\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>對管理者來說，alpha notes 很像預警清單。你不一定會部署 alpha，但你可以用它確認哪些平台假設正在消失，提早修正映像、節點基底與部署腳本，避免之後升級時才發現不相容。\u003C\u002Fp>\u003Cul>\u003Cli>Amazon Linux 2 支援在 alpha 中移除\u003C\u002Fli>\u003Cli>舊 mirror 項目被清理\u003C\u002Fli>\u003Cli>測試與 scenario 持續更新\u003C\u002Fli>\u003Cli>適合拿來做前置規劃\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>4. 下載資產把主要平台都列出來了\u003C\u002Fh2>\u003Cp>v1.35.1 的 release assets 涵蓋 darwin、linux、windows，而且同時提供 amd64 與 arm64 版本。這對直接從 \u003Ca href=\"\u002Ftag\u002Fgithub\">GitHub\u003C\u002Fa> release 下載 kOps 的團隊很重要，因為你不用猜支援範圍，頁面本身就把可用的二進位檔列清楚了。\u003C\u002Fp>\u003Cp>另外還有 SHA256 檔案，這是實務上最常用的完整性驗證步驟。若你有自動化安裝流程，先驗 hash 再部署，可以少掉很多因下載損毀或來源不一致造成的問題。\u003C\u002Fp>\u003Ccode>kops-linux-amd64\nkops-linux-arm64\nkops-darwin-amd64\nkops-darwin-arm64\nkops-windows-amd64\n*.sha256\u003C\u002Fcode>\u003Ch2>5. 這版偏修補，不是偏新功能\u003C\u002Fh2>\u003Cp>v1.35.1 的 changelog 大多是修正與維護項目，像是 control plane availability 檢查、instance requirements、kubeconfig 處理、Cilium flags、GCE 清理，以及控制器相關 bug fix。這種組合通常代表發行重心在穩定性，而不是推出大量新功能。\u003C\u002Fp>\u003Cp>對生產環境來說，這是相對好消化的版本類型。當你已經知道自己的叢集架構，卻想把已知問題修掉、把升級風險壓低，這種 fix-heavy release 往往比功能導向版本更適合先採用。\u003C\u002Fp>\u003Cul>\u003Cli>control plane availability 修正\u003C\u002Fli>\u003Cli>instance requirements 修正\u003C\u002Fli>\u003Cli>kops reconcile cluster 新增 --use-kubeconfig\u003C\u002Fli>\u003Cli>多個雲平台特定 bug fix\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>怎麼挑\u003C\u002Fh2>\u003Cp>如果你要的是目前最穩的正式版，先看 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkops\u002Freleases\u002Ftag\u002Fv1.35.1\">v1.35.1\u003C\u002Fa>。如果你在做下一輪升級規劃，先讀 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkops\u002Freleases\u002Ftag\u002Fv1.36.0-alpha.1\">v1.36.0-alpha.1\u003C\u002Fa>，因為它會先告訴你哪些東西即將被移除。若你的叢集還有 Kubernetes 1.30，支援退場就是你現在要排進時程的工作。\u003C\u002Fp>\u003Cp>簡單說，日常維護選 v1.35.1，前瞻規劃看 alpha notes，版本淘汰則拿來決定升級順序。這樣你就能在 kOps 1.36 到來前，把風險先處理掉。\u003C\u002Fp>","5 個 kOps 版本重點，涵蓋 v1.35.1 修補、Kubernetes 1.30 淘汰時程，以及升級前該看的信號。","github.com","https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkops\u002Freleases",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780586284483-09lo.png","industry","zh","d363daa8-9b53-496b-9124-4ddd68900729",[17,18,19,20,21,22,23,24],"kOps","Kubernetes","release notes","v1.35.1","v1.36.0-alpha.1","upgrade","deprecation","cluster admin",[26,27,28],"v1.35.1 是目前頁面上的最新穩定版，重點在修補與維護。","Kubernetes 1.30 支援會在 kOps 1.36 移除，應立即規劃升級。","v1.36.0-alpha.1 可用來提前看見移除項目與相容性風險。",0,"2026-06-04T15:17:30.309022+00:00","2026-06-04T15:17:30.291+00:00","20d09c2d-324d-4e0e-b034-3d4415f46e6e",{"tags":34,"relatedLang":45,"relatedPosts":49},[35,37,39,41,43],{"name":19,"slug":36},"release-notes",{"name":18,"slug":38},"kubernetes",{"name":21,"slug":40},"v1360-alpha1",{"name":20,"slug":42},"v1351",{"name":17,"slug":44},"kops",{"id":15,"slug":46,"title":47,"language":48},"5-kops-release-notes-for-kubernetes-admins-en","5 kOps release notes for Kubernetes admins","en",[50,56,62,68,74,80],{"id":51,"slug":52,"title":53,"cover_image":54,"image_url":54,"created_at":55,"category":13},"f8ff68f8-1cca-4db8-b871-c7b0fdf8eeb5","4-takeaways-from-cloudflares-ai-first-reset-zh","4 個關於 Cloudflare AI-first 重整的重點","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780589879946-i7e3.png","2026-06-04T16:17:28.780759+00:00",{"id":57,"slug":58,"title":59,"cover_image":60,"image_url":60,"created_at":61,"category":13},"f1822ffc-fbe1-4c5f-aa5d-e6dc37ae54a5","5-ways-harriet-sperling-echoes-kate-middleton-zh","5 種 Harriet Sperling 與凱特王妃的相似之處","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780587192008-dmzo.png","2026-06-04T15:32:45.790575+00:00",{"id":63,"slug":64,"title":65,"cover_image":66,"image_url":66,"created_at":67,"category":13},"4d970649-387b-4b0d-ac24-1a8d656c012b","5-wild-news-beats-seth-meyers-recap-zh","5 個 Seth Meyers 失控新聞節拍","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780583582839-kwpn.png","2026-06-04T14:32:23.749403+00:00",{"id":69,"slug":70,"title":71,"cover_image":72,"image_url":72,"created_at":73,"category":13},"94605094-9f4d-4b99-baaf-77cf5f4720ee","why-openai-is-right-to-push-back-on-white-house-ai-safety-ru-zh","為什麼 OpenAI 這次反對白宮 AI 安全規則是對的","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780581772675-1sey.png","2026-06-04T14:02:20.587136+00:00",{"id":75,"slug":76,"title":77,"cover_image":78,"image_url":78,"created_at":79,"category":13},"cad99049-9883-450d-84f5-6ed92a7c51d3","wolters-kluwer-deepens-openai-deal-stock-slips-zh","Wolters Kluwer 加深 OpenAI 合作","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780570971912-870u.png","2026-06-04T11:02:25.638893+00:00",{"id":81,"slug":82,"title":83,"cover_image":84,"image_url":84,"created_at":85,"category":13},"046d62be-05e2-47ff-908b-b0bfa603ae35","5-cuda-13-3-updates-for-gpu-developers-zh","5 個 CUDA 13.3 GPU 開發更新","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1780568291192-epf6.png","2026-06-04T10:17:44.229366+00:00",[87,92,97,102,107,112,117,122,127,132],{"id":88,"slug":89,"title":90,"created_at":91},"ee073da7-28b3-4752-a319-5a501459fb87","ai-in-2026-what-actually-matters-now-zh","2026 AI 真正重要的事","2026-03-26T07:09:12.008134+00:00",{"id":93,"slug":94,"title":95,"created_at":96},"83bd1795-8548-44c9-9a7e-de50a0923f71","trump-ai-framework-power-speech-state-preemption-zh","川普 AI 框架瞄準電力、言論與州權","2026-03-26T07:12:18.695466+00:00",{"id":98,"slug":99,"title":100,"created_at":101},"ea6be18b-c903-4e54-97b7-5f7447a612e0","nvidia-gtc-2026-big-ai-announcements-zh","NVIDIA GTC 2026 重點拆解","2026-03-26T07:14:26.62638+00:00",{"id":103,"slug":104,"title":105,"created_at":106},"4bcec76f-4c36-4daa-909f-54cd702f7c93","claude-users-spreading-out-and-getting-better-zh","Claude 用戶更分散，也更會用","2026-03-26T07:22:52.325888+00:00",{"id":108,"slug":109,"title":110,"created_at":111},"bd903b15-2473-4178-9789-b7557816e535","openclaw-raises-hard-question-for-ai-models-zh","OpenClaw 逼問 AI 模型價值","2026-03-26T07:24:54.707486+00:00",{"id":113,"slug":114,"title":115,"created_at":116},"eeac6b9e-ad9d-4831-8eec-8bba3f9bca6a","gap-google-gemini-checkout-fashion-search-zh","Gap 把結帳搬進 Gemini","2026-03-26T07:28:23.937768+00:00",{"id":118,"slug":119,"title":120,"created_at":121},"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":123,"slug":124,"title":125,"created_at":126},"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":128,"slug":129,"title":130,"created_at":131},"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":133,"slug":134,"title":135,"created_at":136},"191d9b1b-768a-478c-978c-dd7431a38149","mistral-ai-faces-its-hardest-year-yet-zh","Mistral AI 迎來最硬的一年","2026-03-26T07:40:23.716374+00:00"]