Hi, FWIW: I had a similar issue when using a secret with an SSH private key as source secret, when the key entry was not named "ssh-privatekey" but something else. Because of this OpenShift could not determine the type of authentication to use. My working secret now: apiVersion: v1 data: ssh-privatekey: ... kind: Secret metadata: name: bitbucket-login-lsc2-worker type: Opaque So, the secret entry holding your credentials might have an invalid name too? Maybe crosscheck the entry name with a secret that you know is working? Cheers, Oliver