Cherry-pick #16063 to 7.x: Make use of secure port when accessing Kubelet API #16101
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 #16063 to 7.x branch. Original message:
What does this PR do?
This PR switches Metricbeat k8s manifests and docs to point to Kubelet secure port over https instead of the insecure port.
Why is it important?
Insecure port of Kubelet (10255/TCP) is now less common and discouraged and also in most cases it is not enabled by default (requiring to restart
kubelet
with--read-only-port
flag)Checklist
I have added tests that prove my fix is effective or that my feature worksRelated issues