NVIDIA / NVIDIA/holodeck

feat(provisioner): sshConfig support for cluster mode

Open
#855 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
30
Forks
17
No merged PRs in 30d

Description

Additional items from the final re-review (fold into this issue's scope)

  • status --live on a cluster env silently swallows the sshConfig rejection (cmd/cli/status/status.go:235 if err == nil drops the error; reachable only via hand-edited cache today) — surface it with a log line when cluster sshConfig support lands.
  • connectTimeout is silently inert under a bastion transport (hop-2 rides the hop-1 SSH channel); add a doc qualifier or wire a bastion-aware timeout when designing cluster/bastion semantics.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing cluster-mode provisioner handling for sshConfig and the bastion transport semantics. Inspect cmd/cli/status/status.go:235, where status --live currently drops the rejection error. Done means cluster sshConfig support is implemented, the rejection is surfaced there, and connectTimeout behavior under bastion transport is documented or handled.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.