I use MetalLB and the comparison table somewhat confuses me.
> Expose default type of services (ClusterIP) external
What's the use case of this? ClusterIP, by API definition, is used within the cluster. If I need to expose something to external, I use a LoadBalancer service.
> Frontend IP Address sharing
The table says MetalLB cannot do this. But isn't it just: https://metallb.universe.tf/usage/#ip-address-sharing ?
> Auto-add Kubernetes nodes
MetalLB speakers are commonly deployed as daemonsets. When a new node joins a cluster, the speaker will be deployed onto it by the daemonset controller. Isn't that what "auto-add" means? What kind of auto-add functionality does MetalLB miss?
With that said, software LBs do have a lot of issues, and this is a pretty interesting approach.
> Expose default type of services (ClusterIP) external
What's the use case of this? ClusterIP, by API definition, is used within the cluster. If I need to expose something to external, I use a LoadBalancer service.
> Frontend IP Address sharing
The table says MetalLB cannot do this. But isn't it just: https://metallb.universe.tf/usage/#ip-address-sharing ?
> Auto-add Kubernetes nodes
MetalLB speakers are commonly deployed as daemonsets. When a new node joins a cluster, the speaker will be deployed onto it by the daemonset controller. Isn't that what "auto-add" means? What kind of auto-add functionality does MetalLB miss?
With that said, software LBs do have a lot of issues, and this is a pretty interesting approach.