Should certain commands skip the remote version check and use some default kubectl?

[dnwe]

For example local-only things such as kubectl config ... commands to fetch or switch the current context, or print the local config, shouldn't really attempt to do a remote kubectl version match before running and should just pick a default kubectl available locally and run via that

[alisamji-ybor]

Seconded. This is really messing with some of the internal dev tooling we are building at my job.

[flavio]

This is a valid request.

Based on what you said, I would propose:

• completion
• config
• version
• plugin

Am I missing something

[dnwe]

LGTM!