🐛 Cache: Keep selectors when byObject.Namespaces is defaulted #2747
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.
Prior to this patch, configuring for example a labelSelector in
ByObject
and then inheriting namespaces fromDefaultNamespaces
meant that thelabelSelector
would be ignored. This is because if namespaces are configured, we set p a multinamespace cache. If we do that, we expect each namespace entry to have the appropriate selectors configured.Unfortunately we defaulted the configs for
byObject.Namespaces
before defaultingbyObject.Namespace
itself, causing the above-described issue.This change also adds a couple more tests for the cache defaulting.