kubernetes-sigs/kubespray

Update metallb

Open

#13,126 建立於 2026年3月25日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)HTML (10,380 star) (4,419 fork)batch import
help wantedkind/feature

描述

What would you like to be added

Metallb included is dated Oct 20, 2023, there was a few releases back then. Any specific reason to use an d version? Shouldn't be keep update?

Why is this needed

Just to make sure use latest technology available, general bugfix from streamline package and maintain high level of security I think packages should be updated to reflect state of art of their own lifecycle

貢獻者指南

技術棧
pythongo
領域
devopsinfrastructure
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of KubernetesFamiliarity with Kubespray configuration
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
First, identify the current metallb version pinned in Kubespray by searching for 'metallb' in roles or inventory files (e.g., roles/network plugin/metallb/defaults/main.yaml). Then, check the metallb GitHub releases for the latest stable version and any breaking changes. Update the version string accordingly and verify that no other dependencies conflict. Optionally, run kubespray's CI tests if available.