[SSH Node Pools] `apiService.sshNodePools` changes aren't propagated to `~/.sky/ssh_node_pools.yaml` api server file, during a helm deployment.

[sledress]

Description

When updating a node pool configuration in the values.yaml file, changes are not propagated to the api server ~/.sky/ssh_node_pools.yaml file, even after a complete redeployment.

WorkAround

We had to edit the file directly on the pod, and then redeploy the api server.

Addintional Info

Using ArgoCD deployment using helm charts. Default values overriden in a custom values.yaml file.

[Michaelvll]

Hmm, this is unexpected, we do have a few deployments with ssh node pool, and the update seems working in our case, but we do have to include the following field to ensure the ssh config to take effect during update (this is being fixed)

apiService:
  preDeployHook: |
    mkdir -p /root/.ssh
    echo "Linking ssh keys to /root/.ssh"
    for file in /var/skypilot/ssh_keys/*; do
      if [ -f "$file" ]; then
        filename=$(basename "$file")
        ln -sf "$file" "/root/.ssh/$filename"
      fi
    done