In kube-vip/kube-vip#811 , the downward API is used to set the nodeName config flag to the kubernetes node name.
This was an important fix, but only applied via the YAML generator, not in the helm chart.
This is another case of incurring a cost with diverging deployment methods.
In the helm chart you can do e.g.
envValueFrom:
# Explicitly use the k8s node name (kubectl get node) as the identifier for matching endpointslices.
# See https://github.com/kube-vip/kube-vip/pull/811
vip_nodename:
fieldRef:
fieldPath: spec.nodeName
In kube-vip/kube-vip#811 , the downward API is used to set the nodeName config flag to the kubernetes node name.
This was an important fix, but only applied via the YAML generator, not in the helm chart.
This is another case of incurring a cost with diverging deployment methods.
In the helm chart you can do e.g.