/index.html Recent content in MetalLB on MetalLB, bare metal load-balancer for Kubernetes Hugo -- gohugo.io en-us /concepts/index.html Mon, 01 Jan 0001 00:00:00 +0000 /concepts/index.html MetalLB hooks into your Kubernetes cluster, and provides a network load-balancer implementation. In short, it allows you to create Kubernetes services of type LoadBalancer in clusters that don’t run on a cloud provider, and thus cannot simply hook into paid products to provide load balancers. It has two features that work together to provide this service: address allocation, and external announcement. Address allocation In a Kubernetes cluster on a cloud provider, you request a load balancer, and your cloud platform assigns an IP address to you. /installation/index.html Mon, 01 Jan 0001 00:00:00 +0000 /installation/index.html Before starting with installation, make sure you meet all the requirements. In particular, you should pay attention to network addon compatibility. If you’re trying to run MetalLB on a cloud platform, you should also look at the cloud compatibility page and make sure your cloud platform can work with MetalLB (most cannot). There are three supported ways to install MetalLB: using plain Kubernetes manifests, using Kustomize, or using Helm. Preparation If you’re using kube-proxy in IPVS mode, since Kubernetes v1. /configuration/index.html Mon, 01 Jan 0001 00:00:00 +0000 /configuration/index.html MetalLB remains idle until configured. This is accomplished by creating and deploying various resources into the same namespace (metallb-system) MetalLB is deployed into. There are various examples of the configuration CRs in configsamples. Also, the API is fully documented here. Note If you installed MetalLB with Helm, you will need to change the namespace of the CRs to match the namespace in which MetalLB was deployed. Defining the IPs to assign to the Load Balancer services In order to assign an IP to the services, MetalLB must be instructed to do so via the IPAddressPool CR. /usage/index.html Mon, 01 Jan 0001 00:00:00 +0000 /usage/index.html After MetalLB is installed and configured, to expose a service externally, simply create it with spec.type set to LoadBalancer, and MetalLB will do the rest. MetalLB attaches informational events to the services that it’s controlling. If your LoadBalancer is misbehaving, run kubectl describe service <service name> and check the event log. Requesting specific IPs MetalLB respects the spec.loadBalancerIP parameter, so if you want your service to be set up with a specific address, you can request it by setting that parameter. /faq/index.html Mon, 01 Jan 0001 00:00:00 +0000 /faq/index.html Can I have several address pools? Yes, a given IPAddressPool can allocate multiple IP ranges, and you can have multiple instances, for example: apiVersion: metallb.io/v1beta1 kind: IPAddressPool metadata: name: first-pool namespace: metallb-system spec: addresses: - 192.168.10.0/24apiVersion: metallb.io/v1beta1 kind: IPAddressPool metadata: name: second-pool namespace: metallb-system spec: addresses: - 192.168.9.1-192.168.9.5 - fc00:f853:0ccd:e799::/124You can even specify which pool to draw from using their name. See usage for using annotations to specify which IP pool and address as part of defining your LoadBalancer. /troubleshooting/index.html Mon, 01 Jan 0001 00:00:00 +0000 /troubleshooting/index.html General concepts MetalLB’s purpose is to attract traffic directed to the LoadBalancer IP to the cluster nodes. Once the traffic lands on a node, MetalLB’s responsibility is finished and the rest should be handled by the cluster’s CNI. Because of that, being able to reach the LoadBalancerIP from one of the nodes doesn’t prove that MetalLB is working (or that it is working partially). It actually proves that the CNI is working. /community/index.html Mon, 01 Jan 0001 00:00:00 +0000 /community/index.html We would love to hear from you! Here are some places you can find us. Mailing list Our mailing list is metallb-users@googlegroups.com. It’s for discussions around MetalLB usage, community support, and developer discussion (although for the latter we mostly use GitHub directly). Slack For a more interactive experience, we have the #metallb slack channel on k8s.slack.com. If you’re not already logged into the Kubernetes slack organization, you’ll need to request an invite before you can join. /release-notes/index.html Mon, 01 Jan 0001 00:00:00 +0000 /release-notes/index.html Version 0.16.1 Bug or Regression Fix helm chart rendering issue when default values are provided. (#3058, @fedepaol) Fixed BGPPeer v1beta2 schema: localASN now correctly declares format: int64 (was int32, which cannot represent the declared Maximum=4294967295). (#3054, @lexfrei) Fixed controller health probes and the health bind address is now configurable and defaults to all interfaces (#3062, @Jakob3xD) Helm chart: pod-level prometheus.io/scrape annotations, the PodMonitor endpoints, and the annotation-only Service objects bundled with the ServiceMonitor now all emit scheme: https to match the HTTPS-only metrics endpoint introduced in v0. /apis/index.html Mon, 01 Jan 0001 00:00:00 +0000 /apis/index.html API Reference Packages metallb.io/v1beta1 metallb.io/v1beta2 metallb.io/v1beta1 Resource Types BFDProfile BGPAdvertisement Community ConfigurationState IPAddressPool L2Advertisement ServiceBGPStatus ServiceL2Status BFDProfile BFDProfile represents the settings of the bfd session that can be optionally associated with a BGP session. Field Description apiVersion string metallb.io/v1beta1 kind string BFDProfile kind string Kind is a string value representing the REST resource this object represents.Servers may infer this from the endpoint the client submits requests to.Cannot be updated.In CamelCase.More info: https://git. /prometheus-metrics/index.html Mon, 01 Jan 0001 00:00:00 +0000 /prometheus-metrics/index.html MetalLB exposes different Prometheus metrics that are listed below. MetalLB Allocator Addresses metrics Name Description metallb_allocator_addresses_in_use_total Number of IP addresses in use, per pool metallb_allocator_addresses_total Number of usable IP addresses, per pool MetalLB K8S client metrics Name Description metallb_k8s_client_updates_total Number of k8s object updates that have been processed metallb_k8s_client_update_errors_total Number of k8s object updates that failed for some reason metallb_k8s_client_config_loaded_bool 1 if the MetalLB configuration was successfully loaded at least once metallb_k8s_client_config_stale_bool 1 if running on a stale configuration, because the latest config failed to load MetalLB BGP metrics These metrics are emitted with the metallb_bgp_ prefix in both native BGP mode (by the speaker) and the deprecated FRR mode (by the FRR metrics sidecar). /metallb/index.html Mon, 01 Jan 0001 00:00:00 +0000 /metallb/index.html