Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "k2s node exec" Command #854

Open
jgriegershs opened this issue Nov 11, 2024 · 0 comments
Open

Add "k2s node exec" Command #854

jgriegershs opened this issue Nov 11, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request triaged This issue was discussed in the maintainers round

Comments

@jgriegershs
Copy link
Collaborator

jgriegershs commented Nov 11, 2024

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 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.

See also discussion #787.

Predecessor to #856.

@jgriegershs jgriegershs self-assigned this Nov 11, 2024
@krotz-dieter krotz-dieter added enhancement New feature or request triaged This issue was discussed in the maintainers round labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triaged This issue was discussed in the maintainers round
Projects
None yet
Development

No branches or pull requests

2 participants