You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: