operator: fix the behaviors of xxxScrapeConfigSelector
and xxxNamespaceSelector
#1174
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.
based on rules here
vmagentSpec.selectAllByDefault=false
, sincevmagent.IsUnmanaged()
didn't include checks about VMScrapeConfig. But VMScrapeConfig could be pick up in vmagent's reconcile.xxxNamespaceSelector
matches nothing butselectAllByDefault=true
. Before, it ignores thexxxNamespaceSelector
that matches nothing.IsUnmanaged
check scope in reconcile for each scrape CR.