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
1. Describe IN DETAIL the feature/behavior/change you would like to see.
Current behavior:
$ kops version --server
Client version: 1.28.4 (git-v1.28.4)
Last applied server version: No cluster selected
Proposed behavior:
$ kops version --server
Client version: 1.28.4 (git-v1.28.4)
Last applied server version: 1.28.4
Unless an explicit --name <name> argument is provided, it won't work.
2. Feel free to provide a design supporting your feature request.
Assume current context by default.
(and maybe kops version should also show server version by default? that's questionable though, as it will introduce the delay caused by querying the server.)
The text was updated successfully, but these errors were encountered:
it doesn't use current context as default value and requires --name <name> to be specified explicitly.
Not sure why this happens, probably not hard to fix.
shapirus
changed the title
"kops version" should also show kops server version
"kops version --server" should assume current context by default
May 21, 2024
it doesn't use current context as default value and requires --name <name> to be specified explicitly.
Not sure why this happens, probably not hard to fix.
I went ahead and edited the title and first post to reflect this, now that I discovered the --server option, to avoid wasting bytes and opening a new issue :).
/kind feature
1. Describe IN DETAIL the feature/behavior/change you would like to see.
Current behavior:
Proposed behavior:
Unless an explicit
--name <name>
argument is provided, it won't work.2. Feel free to provide a design supporting your feature request.
Assume current context by default.
(and maybe
kops version
should also show server version by default? that's questionable though, as it will introduce the delay caused by querying the server.)The text was updated successfully, but these errors were encountered: