You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried re-creating the secret several times but continued to get this error each time I used the secret approach (following the docs here).
Had to eventually hard-code the private key and integration ID directly in the values file to get the operator to work again.
I did this routine back-and-forth several times (use existingSecret, hard-code the privateKey and integrationId). After toggling these configs/settings and re-deploying the operator with each, only the hard-coded values seems to work. I even went as far as copying the secret that was created by the Helm chart and still saw the pem encoding error. Only hard-coding seems to work now.
Curious if other folks have seen this behavior. I saw in another issue that this has come up before.
All configs/resources are in the same namespace.
The text was updated successfully, but these errors were encountered:
Curious if anyone else is seeing this behavior:
Over the weekend our runner pool was not available, did some initial digging in logs and found the runner operator throwing the following error:
Tried re-creating the secret several times but continued to get this error each time I used the secret approach (following the docs here).
Had to eventually hard-code the private key and integration ID directly in the values file to get the operator to work again.
I did this routine back-and-forth several times (use
existingSecret
, hard-code theprivateKey
andintegrationId
). After toggling these configs/settings and re-deploying the operator with each, only the hard-coded values seems to work. I even went as far as copying the secret that was created by the Helm chart and still saw the pem encoding error. Only hard-coding seems to work now.Curious if other folks have seen this behavior. I saw in another issue that this has come up before.
All configs/resources are in the same namespace.
The text was updated successfully, but these errors were encountered: