Add filter chain discovery to the relay #703
Merged
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
XAMPPRocky
requested review from
markmandel,
No-ops,
rezvaneh and
vallfors
as code owners
XAMPPRocky
force-pushed
the
ep/relay-filterchain
branch
from
9a7b137 to
889b4bb
Compare
XAMPPRocky
force-pushed
the
ep/relay-filterchain
branch
from
889b4bb to
2134a2e
Compare
markmandel
approved these changes
Feb 16, 2023
|
Build Succeeded 🥳 Build Id: 596e381c-0fd9-46a4-8318-c6bfeb47cb08 The following development images have been built, and will exist for the next 30 days: To build this version: |
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.
This PR refactors out the reflectors of that's used for the control plane into discrete functions in order to allow for the relay to just query for the filter configmap to get the filters for all proxies.
This implementation is just a good enough implementation for now, I think we'll build a more generic interface for the providers with this as a followup as part of #700