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,560,605
Community Members
 
Community Events
185
Community Groups

Why does the sample bitbucket-pipelines runner kubernetes yaml use a Job instead of a Deployment?

The sample kubernetes yaml for the bitbucket-pipelines runner is at https://support.atlassian.com/bitbucket-cloud/docs/pipelines-runners-frequently-asked-questions/#How-do-I-setup-Pipelines-Runner-with-Kubernetes.

 

It uses a Job type instead of a Deployment or Statefulset.  Jobs generally appear to be built for tasks that run and finish, whereas a Deployment can handle updates, recover from crashes more reliably, and seems to be the go-to strategy for most tools.

Are there considerations that would prevent the runner to be deployed as a Deployment?

1 answer

@Matthew Wynn 

 

Thank you for your question!

The self hosted runners are like a daemons that starts, doing work and finish.

It's just an example and it's up to you how to configure you k8s cluster.

 

Best regards,
Oleksandr Kyrdan

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events