Repository: grafana/k6-operator (go)

Issue:
k6.spec.separate also applies affinity to starter-pod 
### Brief summary

Hi, 

it seems that when separating runners to different nodes, the starter-pod is also been scheduled on its own node. Is this intended?

### k6-operator version or image

0.0.8

### K6 YAML

apiVersion: k6.io/v1alpha1
kind: K6
metadata:
  name: k6-test
spec:
  parallelism: 2
  separate: true


### Other environment details (if applicable)

_No response_

### Steps to reproduce the problem

Deploy k6 CRD with separate=true

### Expected behaviour

AntiAffinity should only affect runner-pods not initializer and starter

### Actual behaviour

AntiAffinity is applied to runner and starter pods

Pull request:
Add runner=true label to matchedExpressions in podAntiAffinity
Hi,
this PR fixes scheduling of starter-Pod when using `spec.separater=true` by adding `runner=true` to matched Label-Expressions in podAntiAffinity.


Fixes #168 

Patch:
diff --git a/pkg/resources/jobs/runner.go b/pkg/resources/jobs/runner.go
index d9e17d8..48d0c90 100644
--- a/pkg/resources/jobs/runner.go
+++ b/pkg/resources/jobs/runner.go
@@ -231,6 +231,13 @@ func newAntiAffinity() *corev1.Affinity {
 									"k6",
 								},
 							},
+							{
+								Key:      "runner",
+								Operator: "In",
+								Values: []string{
+									"true",
+								},
+							},
 						},
 					},
 					TopologyKey: "kubernetes.io/hostname",


Test patch:
diff --git a/pkg/resources/jobs/runner_test.go b/pkg/resources/jobs/runner_test.go
index bd45fa5..2c6498f 100644
--- a/pkg/resources/jobs/runner_test.go
+++ b/pkg/resources/jobs/runner_test.go
@@ -174,6 +174,13 @@ func TestNewAntiAffinity(t *testing.T) {
 									"k6",
 								},
 							},
+							{
+								Key:      "runner",
+								Operator: "In",
+								Values: []string{
+									"true",
+								},
+							},
 						},
 					},
 					TopologyKey: "kubernetes.io/hostname",