When a secret in the metallb-system ns changes, all the configurations (and thus, the services) gets reprocessed. This causes unnecessary churn and announcements spread around. This is the case, for example, of the memberlist secret but it applies to any secret belonging to that ns (regardless of the fact that it's associated to  a bgp peer password or not)

Always

1. Create a metallb configuration
2. Create a random secret in the metallb's ns
3. Observe the logs / events

Config / services are reprocessed, services are reannounced (which results in new frr configs / gratuitous arps)

Nothing happens because the config didn't change