-
Notifications
You must be signed in to change notification settings - Fork 548
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
rpk cli missing redpanda on MacOS #3666
Comments
thanks @scallister. Redpanda only runs natively on Linux. For macOS, please check |
@ivotron you are right, but the concern that a user from a mac computer should be able to send an admin command to a redpanda cluster to decomission a node
I think we may move the broker decomission to a build-path that is non linux only tho. it makes sense to me to be able to decomission a node from a non linux box. |
cc: @vsaraswat for visibility |
Agree--Mac users should be able to talk to remote clusters. |
i see, yeah, that makes todal sense. thanks for clarifying! |
/backport v21.11.x |
Version & Environment
Redpanda version: (use
rpk version
):v21.11.3 (rev b3e78b1d5c2cb9d8bb11138738d3e6854cca4802)
v21.11.3 (rev b3e78b1)
What went wrong?
The
redpanda
command, specificallyrpk redpanda admin broker decommission
is missing.What should have happened instead?
The
rpk
tool should have theredpanda
subcommand both in Linux and in Brew. The specific functionality I'm interested in is the ability to decommission servers using the Brew version.How to reproduce the issue?
brew install vectorizedio/tap/redpanda
rpk redpanda --help
rpk
will then fail to have this subcommand.Additional information
I’ve noticed the brew installable version of rpk, v21.11.3 (rev b3e78b1) has different commands than the rpk that ships with Redpanda :thinking_face: v21.11.3 (rev b3e78b1)
For example the redpanda command is missing from the brew version even though that is listed as version 21.11.3.
Brew output:
And then here is the output from the rpk that ships with the debian installed package:
The text was updated successfully, but these errors were encountered: