Setting Peer attributes - Phase 1 #679
Merged
Conversation
This file contains hidden or 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
Attributes are passed to the controlplane thru its cli, and are added to the set of client attributes Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Signed-off-by: Ziv Nevo <nevo@il.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 allows users to set Peer labels (attributes) from the
clusterlink deploy peerCLI.These labels propagate thru
platform.Config, theInstanceCR and the control-plane CLI, all the way to the authz manager, where they are added to the "source" attributes.This is a first step towards solving issue #291 .
Delayed to phase 2:
Each Peer should keep track of attributes of other Peers (possibly by slightly abusing the health check mechanism).
This will allow adding Peer attributes to the "destination" attributes, so Peer attributes can be used in both
fromandtosections of AccessPolicies.