Skip to main content
GET
Get Connection Info

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

cluster_id
string
required

Query Parameters

team_id
string
required

Team the cluster must belong to

Response

Successful Response

SSH coordinates for one Slurm cluster deployment.

Same audience and same resolution as the Model Factory web UI's connect box (modelFactoryClusters.ts listMyWorkloads, which calls buildSlurmSshCommand with the tailnet fallback inputs nulled out): RUNNING deployments get the login coordinates; non-RUNNING ones (the ssh-proxy pod isn't up yet for a PENDING/DEPLOYING release) report connectable=False with null fields.

ssh_command is the authoritative, fully-resolved copy-paste command — identical to what the dashboard renders, with the same bare username placeholder for the caller's cluster login.

ssh_port is Job.publicSshPort, and None means the DEFAULT PORT 22, not "unknown" — same as the dashboard omitting -p. It is never the chart-internal ssh-proxy hostPort (config.sshNodePort), which backs only the tailnet-address fallback the customer surface deliberately does not offer.

When an admin has set a full command override (Job.publicSshCommand — jump hosts, custom identity files), that command is returned verbatim and ssh_host/ssh_port are null: the override is opaque and must not be decomposed into coordinates that may not describe it.

connectable
boolean
required
ssh_host
string | null
ssh_port
integer | null
ssh_command
string | null