Please enable only either the metallb or kube-vip loadbalancer service, but not both.

[YasuhiroABE]

What would you like to be added

Please add a note to disable the kube_vip_services_enabled, when another load balancer service will be used.

I think it's possible to force disable exclusively fixing the ansible role.
However, it will complicate the role by mixing of the different types of variables.

Why is this needed

In my environment, the both of "kube_vip_services_enabled: true" and "metallb_enabled: true" causes the infinite reconcile loop.

Because of the high frequent reconcile process, network connections through the loadbalancer are intermittently disconnected.

I took a little time to find a root cause. So please consider it.

See also: metallb/metallb#2177

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale