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
The existing implementation for executing commands on remote nodes (k2s system ssh m|w) shows bad performance (#639) and is inappropriate for an arbitrary number of nodes.
Solution
Introduce the k2s node exec command similar to the existing k2s node copy command:
k2s node exec [flags]
Flags:
-i, --ip-addr string [required] Node IP address
-u, --username string [required] Username for remote connection
-c, --command string [required] Command to execute on the node
-p, --port uint16 Port for remote connection (default 22)
-t, --timeout string Connection timeout, e.g. '1m20s', allowed time units are 'ns', 'us' (or 'µs'), 'ms', 's', 'm', 'h' (default "30s")
For performance reasons, the already existing Go-based SSH connection shall be used instead of executing the ssh.exe as separate process.
Problem
The existing implementation for executing commands on remote nodes (
k2s system ssh m|w
) shows bad performance (#639) and is inappropriate for an arbitrary number of nodes.Solution
Introduce the
k2s node exec
command similar to the existingk2s node copy
command:For performance reasons, the already existing Go-based SSH connection shall be used instead of executing the
ssh.exe
as separate process.See also discussion #787.
Predecessor to #856.
The text was updated successfully, but these errors were encountered: