can you explain why this change is required and how it is helping if you use the krew plugin to install the tool above change is not required, IIUC you are consuming the release build image and directly calling the binary?

I dont know which is more desired, that is why I propose this change to check (as I see the discrepancy with the homebrew artifact, Homebrew/homebrew-core#171289)

sounds like kubectl-rook-ceph is preferred over kubectl-rook_ceph?

also cc @travisn for thoughts

kubectl-rook_ceph is the correct Name of the binary in order to call the plugin with kubectl rook-ceph.

Offical kubectl Docs:
https://kubernetes.io/docs/tasks/extend-kubectl/kubectl-plugins/#names-with-dashes-and-underscores

That doc indicates that it is "possible" to use underscores, but it is not required. Seems like it is more natural to use dashes, as described earlier in the doc here.

It seems to me that dashes in the filename represents a space in the kubectl command.

the command kubectl foo bar baz is invoked by the user, would have the filename of kubectl-foo-bar-baz.

The commands work fine in our testing with the dash as in the readme. Are you seeing otherwise?

I'm currently on vacation, so I'm unable to test anything. I'm just referring to the Kubernetes documentation, and although dashes currently works, it's not guaranteed to work in the future. I recommend using an underscore.

Just my 2 cents.

So, when using binary directly(not with krew) kubectl-rook-ceph it doesn't read it to kubectl rook-ceph but using the binary name kubectl- rook_ceph it reads it to kubectl rook-ceph

The way to get the right name in help text for a command used as a plugin is documented here:
https://github.com/spf13/cobra/blob/main/site/content/user_guide.md#creating-a-plugin