Label router with Match field for Exclude and Select #357
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tarokkk
changed the title
tarokkk
force-pushed
the
label-router-exclude
branch
from
53d36c6
to
fe40291
Compare
tarokkk
force-pushed
the
label-router-exclude
branch
from
a7b055c
to
b7afd59
Compare
tarokkk
changed the title
ahma
approved these changes
Feb 19, 2020
pepov
approved these changes
Feb 20, 2020
simonkey007
pushed a commit
to simonkey007/logging-operator
that referenced
this pull request
Mar 11, 2021
* initial advanced routing * create v1beta2 api * extend FLow and ClusterFlow instead of API v1beta2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's in this PR?
This PR contains major changes in the CRD spec!
selectorinFlowandClusterFlowThe attribute will still be available however using the
matchfield is preferable.matchDifferently from
selectors, match is a list ofselectandescludestatement. The expressionsevaluated in order and the first positive or negative match will break the evaluation.
Detailed documentation will be available in the docs.
Additional context
With this change we can handle several so far unavailable scenarios of log routing.
Checklist