Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,402
Community Members
 
Community Events
176
Community Groups

Ability to mount custom volumes in self hosted pipelines runner into a build container

Hi Atlassian Community:

We are running self hosted pipelines runner in GKE cluster. We need to pull/push docker images from/to "gcr.io" in a pipeline.

In GKE cluster, we use Kubernetes Service Account + GKE workload identity to allow an application (Kubernetes POD) to be able to access GCP services/resources, including logging in to gcr.io. This is a regular and recommended way to authorise applications to access services/resources in GCP (and AWS/Azure) cloud environment, and it's safer than using a static service account key file or credentials.

With Kubernetes Service Account + GKE Workload Identity, we can login to “gcr.io” in the bitbucket-pipelines-runner and docker:dind containers of a POD. But a build container which is started by bitbucket-pipelines-runner runs as docker in docker. The build container couldn’t access the mounted service account token in bitbucket-pipelines-runner container (i.e. “/var/run/secrets/kubernetes.io/serviceaccount”). As the result, we won’t be able to login to gcr.io within the build container and “docker build/pull/push” in a pipeline fails.

If we could have an ability to mount “/var/run/secrets/kubernetes.io/serviceaccount” into the build container, the issue would be solved.

With this ability, we may also pass some environment related variables into the build container by mounting file(s) without defining them in Bitbucket Cloud workspace/repository variables separately. 

I raised a feature request (https://jira.atlassian.com/browse/BCLOUD-21738) for this. Not sure what's the process for this feature request being picked up?

 

Regards,

Aaron

1 comment

any news about it ?

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events