1. Proposed title of this feature request

Metallb - not having to run a speaker on every node.
2. What is the nature and description of the request?

ATM with Metallb (although not well documented) when `externalTrafficPolicy: Local` Is used on a loadbalancer service only nodes running a Speaker pod + a pod for the service will announce the service  via BGP.

For a lot of deployments, it makes more sense to limit the BGP speakers to a subset of nodes, and have these nodes announce all nexthops in the cluster with valid endpoints.

This is more inline with how a traditional network would be configured, i have never seen a network where every VM has to talk BGP to ingress traffic,  This could be done in FRR using static routes (one route per node per service) then redistributing these via BGP without loading them into the speaker fib.

3. Why does the customer need this? (List the business requirements here)

Some customers can not have every node talking BGP (security/network policy) allowing metallb to act more like a reflector and announce next-hops for every node from a subset of nodes would be much more acceptable and user friendly. 

4. List any affected packages or components.

Metallb