DVO-105: extends the logic of matching "app" labels #252
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.
DVO tries to group objects with the same app label value. Before this update, the operator tried to read the following paths to get the app label value:
metadata.labels.appspec.selector.matchLabels.appThe problem with this approach is that labels can match using matchExpressions. An example is:
which means match everything except of resources with app=foo or app=bar. This is a more effective approach but more complex.
The problem is that we don't know the set of app label values (in a namespace) in advance. So the logic here is to sort the found
GroupVersionKindsaccording their group (this adds theapps/v1group between the first in the slice) and then process theapplabel selectors.