The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
When configuring my Kustomization files, i've decided to use API Token option since the app passwords are being deprecated soon.
No matter what i've tried, my containers always fail to authenticate with following error:
│ ✖ At least one authorization method of (BITBUCKET_USERNAME, BITBUCKET_APP_PASSWORD) or (BITBUCKET_OAUTH_CLIENT_ID, BITBUCKET_OAUTH_CLIENT_SECRET) required. │ │ stream closed EOF for bitbucket-runner-control-plane/runner-controller-564d6979cd-779nc (runner-controller)
I feel like the official runners-autoscaler project is not up to date and/or guidance documents are wrong. What am i missing or what can i do alternatively if i can't use API token?
1 answer
1 accepted
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Based on your other post and c/p-ed kustomization.yaml, i suggest to double check your token scope, and if the base64 conversion is correctly done. Kustomization file you're using is the default one from Atlassian so not much can be done there and it looked fine to me.
I'm using Hashicorp Vault to store my secrets and inject them into my Runners, so the procedure is a bit different on my side.
Feel free to send me some more details and maybe i can help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.