Hey @KOfoegbu - I’ve heard back from our development team with the information below;
We don’t have any documentation on Kubernetes deployments yet, that said we didn’t have to make any modifications to the minion to deploy it to a local cluster.
Below is our example deployment, but you may be looking a deployment with some number of replicas, where the number of replicas will depend on the types of jobs their running and how many of said jobs are running. You can also take a look at our monitoring documentation that’s linked in our Containerised Private Minion install docs to help you figure out how many replicas you would want.
We are seeing some requests to make the Containerised Private Minion more Kubernetes friendly, so we’ll get your request for that added too.
Please find below our sample Kubernetes deployment.
Kubernetes Deployment
apiVersion: apps/v1
kind: Deployment
metadata:
name: containerized-private-minion
spec:
selector:
matchLabels:
app: containerized-private-minion
replicas: 3 # tells deployment to run 3 pods matching the template
template:
metadata:
labels:
app: containerized-private-minion
spec:
containers:
- name: containerized-private-minion
image: quay.io/newrelic/synthetics-minion:latest
volumeMounts:
- mountPath: /var/run
name: docker-sock
- mountPath: /tmp
name: tmp
env:
- name: MINION_PRIVATE_LOCATION_KEY
value: <your key>
- name: MINION_CHECK_TIMEOUT
value: "300"
ports:
- containerPort: 80
volumes:
- name: docker-sock
hostPath:
path: /var/run
- name: tmp
hostPath:
path: /tmp
