You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.