Cherry-pick #14738 to 7.x: Refactor kubernetes autodiscover to enable different resource based discovery #14924
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 #14738 to 7.x branch. Original message:
This PR tries to move around code in a way such that each resource has its own interface implementation and the autodiscover relies on a
resource
parameter to determine what the watcher to spin up and how to create hints. We also now addscope
as a parameter to define if Beats is running either at anode
level or at acluster
level.The above configuration would enable discovering service objects across the cluster.
The above configuration would allow doing pod discovery across the cluster.
closes #14044 and #10578