skypilot-org/skypilot

[SSH] After `helm upgrade`, `sky ssh up` needs to be run again

Open

#7659 opened on Oct 17, 2025

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Python (4,859 stars) (311 forks)batch import
P0good first issuegood starter issues

Description

This issue does not include a description.

Contributor guide

Tech stack
python
Domain
clouddevops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
HelmKubernetesPythonSSH
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate why `sky ssh up` must be rerun after a `helm upgrade`. Start by examining the `sky ssh up` command implementation (likely in `sky/ssh.py`) and how SSH configuration is stored. Review the Helm chart files to see if upgrades reset SSH related resources. Check if there are any existing comments or linked issues in the issue #7659 discussion. Consider if the issue is related to missing post upgrade hooks or configuration persistence. Look for any recent changes in the repository that might have introduced this behavior.