K6-operator did not create the starter pod


i follow the blog Running distributed k6 tests on Kubernetes
what’s wrong?

Hi @wuqiblues,
Welcome to the forum :wave: Could you please be more specific on what went wrong? Your screenshot doesn’t contain any error per se, unless you’re trying to run a script with short duration and starter pod didn’t get created? What steps did you take to deploy and what kind of troubleshooting was used? Perhaps, it’d also be useful to know what kind of cluster you’re using.

Hi Team,
I have the same issue, I am creating custom resource with following code and controller is able to deploy initializer pod and no starter pod is created as below.

I am using Aks cluster and following official k6 doc (config Map approach) - Running distributed tests

Custom resource definition

-------------------------------------
apiVersion: k6.io/v1alpha1
kind: TestRun
metadata:
  name: run-k6-from-configmap
spec:
  parallelism: 4
  script:
    configMap:
      name: my-test
      file: test.js
  runner:
    livenessProbe:
      httpGet:
        path: /v1/status
        port: 6565
      initialDelaySeconds: 30
      periodSeconds: 10
    readinessProbe:
      httpGet:
        path: /v1/status
        port: 6565
      initialDelaySeconds: 30
      periodSeconds: 10
    resources:
      limits:
        cpu: 400m
        memory: 500Mi
      requests:
        cpu: 400m
        memory: 500Mi

Deployment status

I don’t see any errors in k6-operator controller logs, attaching the same for reference.

Please let me know in case of any additional details.

Thanks
Krishna

@iam432 can you share the log of the initializer pod with us?

Hi @bandorko,
Here is the log output of initializer.

$ ku logs run-k6-from-configmap-initializer-cxwpc
{
  "paused": null,
  "vus": 10,
  "duration": "10s",
  "iterations": null,
  "stages": null,
  "scenarios": {
    "default": {
      "executor": "constant-vus",
      "startTime": null,
      "gracefulStop": null,
      "env": null,
      "exec": null,
      "tags": null,
      "vus": 10,
      "duration": "10s"
    }
  },
  "executionSegment": null,
  "executionSegmentSequence": null,
  "noSetup": null,
  "setupTimeout": null,
  "noTeardown": null,
  "teardownTimeout": null,
  "rps": null,
  "dns": {
    "ttl": null,
    "select": null,
    "policy": null
  },
  "maxRedirects": null,
  "userAgent": null,
  "batch": null,
  "batchPerHost": null,
  "httpDebug": null,
  "insecureSkipTLSVerify": null,
  "tlsCipherSuites": null,
  "tlsVersion": null,
  "tlsAuth": null,
  "throw": null,
  "thresholds": null,
  "blacklistIPs": null,
  "blockHostnames": null,
  "hosts": null,
  "noConnectionReuse": null,
  "noVUConnectionReuse": null,
  "minIterationDuration": null,
  "ext": null,
  "summaryTrendStats": [
    "avg",
    "min",
    "med",
    "max",
    "p(90)",
    "p(95)"
  ],
  "summaryTimeUnit": null,
  "systemTags": [
    "check",
    "error",
    "error_code",
    "expected_response",
    "group",
    "method",
    "name",
    "proto",
    "scenario",
    "service",
    "status",
    "subproto",
    "tls_version",
    "url"
  ],
  "tags": null,
  "metricSamplesBufferSize": null,
  "noCookiesReset": null,
  "discardResponseBodies": null,
  "totalDuration": "40s",
  "maxVUs": 10
}

Thanks
Krishna

Hi @iam432, to see controller’s logs in default deployment, you need to pick -c manager container. In your example, you didn’t add that option and logs from another container were shown by default.

By the way, these troubleshooting tricks are now described in this doc:

Could you please try to follow that doc and see if it helps to unearth the issue?