You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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: