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
This seems worth having talosctl issue a warning about:
Maybe it's worth breaking the talosctl invocation when server [major.minor] version > talosctl [major.minor] version ? Such invocation is most times incorrect or even dangerous.
The original idea was to stop some operations if the server (machined) is a higher version than the client (talosctl). That is because such operations can damage installation in the worst case.
Proposed operations:
apply-config
etcd
inject
machineconfig
meta
reset
upgrade
upgrade-k8s
And other modifying machine config and k8s config.
If you have examples of damaging the Talos install, it'd be interesting to see. So far it's more of a UX issue that the command fails until it is in sync with Talos version.
This seems worth having talosctl issue a warning about:
Maybe it's worth breaking the
talosctl
invocation when server [major.minor] version >talosctl
[major.minor] version ? Such invocation is most times incorrect or even dangerous.Originally posted by @vladimirfx in #9469 (comment)
The text was updated successfully, but these errors were encountered: