About this skill

Problem context

In bare-metal environments, MetalLB is often used to provide external load-balancing for Kubernetes services. When integrating MetalLB directly, engineers still need to understand the bare-metal network, routing policy, and service exposure path. This skill wraps Metallb as a Wrapper entry point. It is not a replacement for MetalLB itself; instead, it provides a tool-oriented interface for toolchains, scripts, or automation workflows.

How it works

The skill is positioned as a wrapper tool for the bare-metal load balancer:
- Its description is metallb - Bare metal load balancer (Wrapper), centered on Metallb.
- Tags include tool, github, and automation, indicating an automation tool and GitHub-related workflow orientation rather than a full load-balancer control plane.
- In use, it should be understood as a layer on top of MetalLB, with the cluster network, bare-metal environment, and actual MetalLB availability still doing the real work.

Boundaries

This skill does not automatically resolve routing reachability, IP allocation, node configuration, or MetalLB installation issues. If the target environment lacks proper bare-metal networking, or MetalLB itself is not ready, the wrapper cannot replace low-level network troubleshooting. It is suitable for workflow wrapping, tool invocation, and automation integration; it is not a MetalLB installation manual or network architecture design document.

Screenshots

Use Cases

In bare-metal Kubernetes clusters, route MetalLB tool calls through one wrapper entry for scripts.
In GitHub Actions, invoke a wrapped MetalLB tool item instead of expanding manual commands.
During automation troubleshooting, call MetalLB-related tools from a unified wrapper surface.
When organizing ops tooling, expose MetalLB's tool capability as a recognizable wrapper skill.

Best For

SREs managing bare-metal Kubernetes clusters who need to include MetalLB tool calls in scripts or workflows.
Platform engineers maintaining GitHub automation pipelines who need to reference wrapped MetalLB tool items.
Infrastructure engineers organizing ops toolchains who need to expose tool capabilities as recognizable skill entries.
Backend engineers troubleshooting bare-metal network automation who need a unified entry for related tool calls.