yorugac
commented
1 year ago Hi @sathishkkrishnan, it sounds like you already have a k6 Cloud subscription but the cloud output tests in k6-operator must be enabled additionally for your account. Please write to k6 support to ask them to enable that option for the k6-operator tests: once the option is turned on, you should be able to run these tests right away.
This is not an issue of k6 Operator, AFAIS, but just of configuring subscription. So I'm closing the issue. Please feel free to re-open as needs be.
Brief summary
I deployed k6-operator in Azure AKS. Deployment and test execution is working. However when I tried sending results to cloud, the runner pods are not coming.
Below is the error message from the controller pod
2023-03-23T20:36:01.678Z INFO controllers.K6 Reconcile(); stage = initialization {"namespace": "k6-operator-system", "name": "k6-test-1"} 2023-03-23T20:36:01.693Z INFO controllers.K6 k6 inspect: {External:{Loadimpact:{Name: ProjectID:0}} TotalDuration:45s MaxVUs:2 Thresholds:map[]} {"namespace": "k6-operator-system", "name": "k6-test-1"} 2023-03-23T20:36:01.693Z INFO controllers.K6 Token for k6 Cloud was loaded. {"namespace": "k6-operator-system", "name": "k6-test-1"} 2023-03-23T20:36:02.049Z ERROR controller Reconciler error {"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "name": "k6-test-1", "namespace": "k6-operator-system", "error": "(403/E2) Validation failed\n No active Subscription supports k6 CLI output to k6 Cloud with thresholds processing"} github.com/go-logr/zapr.(zapLogger).Error /go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128 sigs.k8s.io/controller-runtime/pkg/internal/controller.(Controller).reconcileHandler /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:237 sigs.k8s.io/controller-runtime/pkg/internal/controller.(Controller).processNextWorkItem /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:209 sigs.k8s.io/controller-runtime/pkg/internal/controller.(Controller).worker /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:188 k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1 /go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:155 k8s.io/apimachinery/pkg/util/wait.BackoffUntil /go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:156 k8s.io/apimachinery/pkg/util/wait.JitterUntil /go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:133 k8s.io/apimachinery/pkg/util/wait.Until /go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:90
Out to cloud is working perfectly from CLI using the same token. Is this feature not supported from K6-operator? Please help.
k6-operator version or image
Latest
K6 YAML
apiVersion: k6.io/v1alpha1 kind: K6 metadata: name: k6-test-1 spec: parallelism: 1 arguments: --out cloud script: configMap: name: k6-test file: sample.js
Other environment details (if applicable)
No response
Steps to reproduce the problem
Perform make deploy after adding the cloud API token in config/default/kustomization.yaml
Expected behaviour
Test should run and results published to cloud.
Actual behaviour
Runner pods are not starting.