Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bitbucket runners autoscaler doesn't accept API Token authentication

Mert Durukan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 6, 2025

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?

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events