Hi,
We decided to move our Bitbucket runners to our Kubernetes (EKS 1.32) clusters.
I'm using the official guide provided: https://support.atlassian.com/bitbucket-cloud/docs/autoscaler-for-runners-on-kubernetes/
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)
Even though in the documentation and within the kustomization.yaml file it clearly indicated that Option 2 as API token is supported and even encouraged (here's the code link: https://bitbucket.org/bitbucketpipelines/runners-autoscaler/src/8eb4848d0a3eb3f422cdce2854b304da3c78d2bf/kustomize/values/kustomization.yaml#lines-34)
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?
Had the same problem.
⚠️ The image tag (3.7.0) is not up to date.
Try the latest one: 🪧 3.9.0
Thanks you so much for the tip mate!!! it did indeed solve the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm having a issue with that as well, but my problem is with 401. https://community.atlassian.com/forums/Bitbucket-questions/Bitbucket-Autoscaler-Runners-on-Kubernetes-401-Unauthorized/qaq-p/3112182#M120795
Did you follow any specific step to paste the api tokens or just use the echo | base64 command as the doc says?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.