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
fix: configuration of kube-vip per-service leader election
Previously used `enableServicesElection` is not an accepted environment
variable but a field in the kube-vip YAML config file.
* The related environment variable is `svc_election`, which is already
present in the DaemonSet template
* Use `rke2_kubevip_service_election_enable` to set the `svc_election`
in DaemonSet template
* Change default value to `true` to maintain original behavior
Signed-off-by: Tomas Nestrojil <[email protected]>
# Enable layer 4 load balancing for control plane using IPVS kernel module
91
91
# Must use kube-vip version 0.4.0 or later
92
92
93
-
rke2_kubevip_service_election_enable: false
93
+
rke2_kubevip_service_election_enable: true
94
94
# By default ARP mode provides a HA implementation of a VIP (your service IP address) which will receive traffic on the kube-vip leader.
95
95
# To circumvent this kube-vip has implemented a new function which is "leader election per service",
96
96
# instead of one node becoming the leader for all services an election is held across all kube-vip instances and the leader from that election becomes the holder of that service. Ultimately,
# Enable layer 4 load balancing for control plane using IPVS kernel module
52
52
# Must use kube-vip version 0.4.0 or later
53
53
54
-
rke2_kubevip_service_election_enable: false
54
+
rke2_kubevip_service_election_enable: true
55
55
# By default ARP mode provides a HA implementation of a VIP (your service IP address) which will receive traffic on the kube-vip leader.
56
56
# To circumvent this kube-vip has implemented a new function which is "leader election per service",
57
57
# instead of one node becoming the leader for all services an election is held across all kube-vip instances and the leader from that election becomes the holder of that service. Ultimately,
0 commit comments