feat: support both field and label selector in Kubernetes collector #56
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.
Issue:
If the amount of pods reach about 1k in target Kubernetes cluster, the current method to fetch all of pods will be potential to cause CPU SPIKE in API Server.
Enhancement:
2 additional configuration items provided in application.yaml, can be used to limit the search being limited to only one Namespace, to low down the pressure.
Test:
already test in local & UAT env in my company