Why my Konvoy deployment is stuck waiting for SSH target connection to become reachable

Jena Miller

January 31, 2024 02:27
Updated

When deploying a Kubernetes cluster with konvoy, some operators have found that the deployment is stalled at “Verifying that the nodes were provisioned”, specifically waiting for SSH to become available:

TASK [wait-ssh : wait 30 seconds for SSH target connection to become reachable]

This issue usually occurs when the SSH agent is storing several identities. The following command can be used to determine the number of identities:

ssh-add -l

To resolve the issue, the operator should delete the identities and add the SSH key specified in the cluster.yaml (spec.sshCredentials.privateKeyFile) with the following command:

ssh-add -D && ssh-add /path/to/private-key

After deleting and adding the SSH identity, the operator should be able to attempt to deploy once again:

./konvoy up