-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Approve/Reject node membership from CLI #3594
Conversation
Important Auto Review SkippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
2ad899c
to
45fbbb5
Compare
c8b5379
to
3136c3c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
3136c3c
to
c505e8a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO:
Clarify who is allowed to do this.
You can probably leave that to the purview of the authn/z system.
Adds an approve and a reject subcommand to the node command, allowing the user to approve/reject a node's request for cluster membership. This commit adds the foundations for sending other command (like drain, pause etc) to the requester API.
c505e8a
to
37084c7
Compare
This PR adds the ability to approve/reject node membership to the cluster, based on each node's approval state. The approve/reject commands are similar and implemented using the same principle.
it is expected that this same approach can be used for
node pause
andnode drain
etc.Currently the system does nothing to react to the change of state, a future PR will add pubsub for node events so that jobs can be scheduled etc based on approval/rejection/join/leave events.
Additionally this PR resolves a small issue in AuthenticatingClient which was proxying calls with the wrong methods, and adds a basenats test suite for testing against a nats enabled devstack.
TODO: