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

[Feature] Support proxy_jump under ssh_config with fleet YAML config #2010

Closed
peterschmidt85 opened this issue Nov 19, 2024 · 2 comments
Closed

Comments

@peterschmidt85
Copy link
Contributor

peterschmidt85 commented Nov 19, 2024

Setup example:

  1. A login-node that can access SSH into compute-node-1 and compute-node-2.
  2. On a server node, run dstack server
  3. Create a fleet config:
type: fleet
name: private-fleet

placement: cluster

ssh_config:
  hosts:
    - compute-node-1
    - compute-node-2
   proxy_jump: # also can be defined per host; (or it can be a hostname instead of an object)
     hostname: login-node
     identity_file: ~/.ssh/private_key
  1. The dstack apply and dstack attach will try to reuse the jump host SSH config for the specified host (login-node) automatically.

It means the user must have login-node SSH config defined.

Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Dec 20, 2024
Copy link

github-actions bot commented Jan 4, 2025

This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant