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

[Matthew Wynn]

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?

[o_kyrdan]

@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