Cherry-pick #22919 to 7.x: Update k8s client and release k8s lock gracefully #23013
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.
Cherry-pick of PR #22919 to 7.x branch. Original message:
What does this PR do?
Updates k8s go client to utilise a fix so as to gracefully release leader lock.
Why is it important?
To release the leader lease gracefully and make it instantly available for other candidates.
Related issues
How to test this PR locally
kind create cluster --config kind-mutly.yaml
metricbeat-kubernetes-leader.7.11.yaml.txt
Follow the logs of the 2 daemonset pods and kill the one holding the lease. Verify that no errors occur and that the lease was gained by the other Pod.
Verify that basic autodiscovery works along with metadata:
nats.yaml.txt