cleanstart/metallb-controller repository overview

Container Documentation for Metallb-Controller

MetalLB controller container provides Layer 2 and BGP-based load balancing functionality for bare metal Kubernetes clusters. It enables LoadBalancer service types in environments without cloud provider integration, offering enterprise-grade network load balancing capabilities with high availability and automatic failover features.

📌 Base Foundation: Security-hardened, minimal base OS designed for enterprise containerized environments from Cleanstart Registry.

Image Path: Cleanstart/metallb-controller Registry: Cleanstart Registry

Key Features Core capabilities and strengths of this container

• Layer 2 and BGP mode support for network load balancing
• Automatic IP address management and allocation
• High availability configuration with leader election
• Native Kubernetes integration for LoadBalancer services

Common Use Cases Typical scenarios where this container excels

• Bare metal Kubernetes cluster load balancing
• On-premises data center service exposure
• Edge computing network management
• Multi-cluster service load balancing

Pull Latest Image Download the container image from the registry

docker pull cleanstart/metallb-controller:latest

docker pull cleanstart/metallb-controller:latest-dev

Basic Run Run the container with basic configuration

docker run -it --name metallb-controller-test cleanstart/metallb-controller:latest-dev

Production Deployment Deploy with production security settings

docker run -d --name metallb-controller-prod \
  --read-only \
  --security-opt=no-new-privileges \
  --user 1000:1000 \
  cleanstart/metallb-controller:latest

Volume Mount Mount local directory for persistent data

docker run -v $(pwd)/config:/etc/metallb cleanstart/metallb-controller:latest

Port Forwarding Run with custom port mappings

docker run -p 7472:7472 cleanstart/metallb-controller:latest

Environment Variables Configuration options available through environment variables

Security Best Practices Recommended security configurations and practices

• Use RBAC policies to limit controller permissions
• Enable network policies for controller access control
• Configure secure BGP authentication when using BGP mode
• Implement proper IP address pool segmentation
• Regular security audits of MetalLB configuration
• Monitor controller logs for security events
• Use TLS for metrics endpoint communication
• Implement pod security policies

Kubernetes Security Context Recommended security context for Kubernetes deployments

securityContext:
  runAsNonRoot: true
  runAsUser: 65534
  runAsGroup: 65534
  readOnlyRootFilesystem: true
  allowPrivilegeEscalation: false
  capabilities:
    drop: ["ALL"]
    add: ["NET_ADMIN", "NET_RAW"]

⁠Documentation Resources

Essential links and resources for further information

CleanStart Images: https://images.cleanstart.com/⁠

Community Images:
Docker Hub: https://hub.docker.com/u/cleanstart⁠
GitHub: https://github.com/cleanstart-containers⁠
AWS ECR Public Gallery: https://gallery.ecr.aws/cleanstart/⁠

Presence on Social Media:
Community: https://www.linkedin.com/groups/18324021/⁠
YouTube: https://www.youtube.com/@CleanStartOfficial⁠

Contribute to Container Use Cases: https://github.com/cleanstart-dev/cleanstart-use-cases/⁠

Vulnerability Disclaimer

CleanStart offers Docker images that include third-party open-source libraries and packages maintained by independent contributors. While CleanStart maintains these images and applies industry-standard security practices, it cannot guarantee the security or integrity of upstream components beyond its control.

Users acknowledge and agree that open-source software may contain undiscovered vulnerabilities or introduce new risks through updates. CleanStart shall not be liable for security issues originating from third-party libraries, including but not limited to zero-day exploits, supply chain attacks, or contributor-introduced risks.

Security remains a shared responsibility: CleanStart provides updated images and guidance where possible, while users are responsible for evaluating deployments and implementing appropriate controls.