feat(api7): support API-level label selector #150
Merged
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
The current API7 backend uses an implementation that pulls completely and performs label filtering locally. This can be inefficient when the number of potential resources is high.
This PR moves label filtering to the API7 API level, where the server performs resource filtering and only returns resources that match the labeling rules.
It supports the following resource types:
Resource types that will not be supported (These resources do not have a labels field):
Resources that may be supported later:
Even though services do not perform API-level label filtering, label filtering will still work and its mode of operation will fall back to full pull and local filtering. This will be improved later.
Checklist