-
Notifications
You must be signed in to change notification settings - Fork 1
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
Deploy kobectl as kubectl plugin #50
Comments
Since kobectl wraps (as opposed to extending) kubectl, I think it would be either unnecessarily verbose or confusing. If we add a "kobe" subcommand and then the current kobectl syntax follows, it would be unnecessarily verbose. If we adds command to the side of the kubectl ones it would imply that kubectl commands and kobectl commands are to be mixed to perform KOBE-related tasks; which can have unintended effects and invalidates the assumption that the user has not interacted with the cluster in any other way except through kobectl. I am not sure we are actually relying on this assumption as things stand, but I think it is a useful assumption. |
Nowadays, kubectl allows for plugins. Kobectl can also be deployed as such.
The text was updated successfully, but these errors were encountered: