I've been trying to figure this out for days.
- I have a node-red
v1.21.0running in a Kubernetes cluster.
- I'm adding public/private keys to node-red via a secret and gitea user has the same public key verified.
- Key doesn't have a passphrase.
- Attempting to clone the repo project from node-red fails with "Authentication failed".
I have logged into the node-red pod and able to SSH into the Gitea SSH using the key from the
node-red-5767bcd6d4-mn6qs:/data/1$ ssh -i /data/projects/.sshkeys/__default_gitea git@[redacted] PTY allocation request failed on channel 0 Hi there, node-red! You've successfully authenticated with the key named [redacted], but Gitea does not provide shell access. If this is unexpected, please log in with password and setup Gitea under another user. Connection to [redacted] closed.
I have logged into the node-red pod and can clone the target repo using the key from the
$ GIT_SSH_COMMAND="ssh -i /data/projects/.sshkeys/__default_gitea" git clone git@[redacted]:smart-home/node-red.git Cloning into 'node-red'... remote: Enumerating objects: 578, done. remote: Counting objects: 100% (578/578), done. remote: Compressing objects: 100% (245/245), done. remote: Total 578 (delta 371), reused 509 (delta 330), pack-reused 0 Receiving objects: 100% (578/578), 110.47 KiB | 9.21 MiB/s, done. Resolving deltas: 100% (371/371), done.
Using the same key from the UI doesn't work, there are no logs produced by node-red in this case.
Does anyone know what am I doing wrong here?