feat(loadbalancer): add healthCheckNodePort opt-in support #196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR extends the
service.beta.kubernetes.io/scw-loadbalancer-health-check-portannotation (introduced in #195) with support for automatic detection of Kubernetes'healthCheckNodePort.Problem
When using
externalTrafficPolicy: Local, kube-proxy (or cilium) allocates a dedicatedspec.healthCheckNodePorton each node specifically for load balancer health probes. While #195 added the ability to manually specify a health check port, users still had to look up and hardcode thehealthCheckNodePortvalue.Fixes #192
Depends on #195
Solution
Added support for the special value
"auto"which:externalTrafficPolicy: Localandspec.healthCheckNodePortis set → useshealthCheckNodePortnodePort(default behavior)This aligns with native Kubernetes LoadBalancer health check behavior and enables seamless client source IP preservation.
Example Usage
Per-port configuration is also supported:
Future Work
In the next major release,
"auto"will become the default behavior.