Add label select for k8s metadata processor #516
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: longhui.li <[email protected]>
llhhbc
force-pushed
the
add-label-selector-for-k8s
branch
from
708cd65 to
c87f868
Compare
|
Could you please also provide an example of the configuration for selecting specified pods? It seems like you are using a set of "pod's labels" to match the "DataGroup's labels" which contain no k8s metadata when consumed by this processor. |
|
I just ues the struct of kubernetes, It's configable. I will add some examples. |
Signed-off-by: longhui.li <[email protected]>
|
@dxsup I have add some docs |
|
@dxsup Can this be merged? |
|
Sorry for the late reply. I guess the intention of this PR is to filter the |
|
ok |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Add label selector for k8s metadata processor.
For only need watch some pod by label selector.
I'm not sure if I should limit which pods to fetch only in origin.
Related Issue
Motivation and Context
How Has This Been Tested?