kubernetes-sigs/kubespray

Update metallb

Open

#13126 opened on Mar 25, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)HTML (10,380 stars) (4,419 forks)batch import
help wantedkind/feature

Description

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

Contributor guide

Tech stack
pythongo
Domain
devopsinfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of KubernetesFamiliarity with Kubespray configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
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.