-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"no matches for kind \"K6\" in sigs.k8s.io/controller-runtime/pkg/internal/source.(*Kind[...]).Start.func1.1" even with TestRun usage #518
Comments
@robooo, what is the Helm chart version? |
@yorugac, 3.10.2
which cause CrashLoopBackOff 1 of the pods of operator. |
i'm having the same problem with 3.10.1 |
same problem, helm k6-operator-3.10.2 |
I have the same issue but only with chart 3.10.2. |
Thanks for the clarifications, @robooo and everyone! The 3.10.2 chart is indeed broken 😞 It already has removal of Please update to 3.11.0: $ helm repo update
...
$ helm upgrade k6-operator grafana/k6-operator
...
$ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
k6-operator default 4 2025-01-29 19:35:30.657418979 +0200 EET deployed k6-operator-3.11.0 0.0.19 @shehzadqureshi, I'm not sure why you had a problem with 3.10.1: AFAIS, that chart is fine with default values. Either way, it makes sense to update to 3.11 now. |
@yorugac thank you for a fast fix! |
Brief summary
Hi,
I'm deploying operator with terraform like:
and kubernetes deployment starts with:
It was working until today, I'm getting error:
what is wrong here please?
k6-operator version or image
ghcr.io/grafana/k6-operator:controller-v0.0.18
Helm chart version (if applicable)
3.10.2
TestRun / PrivateLoadZone YAML
apiVersion: k6.io/v1alpha1
kind: TestRun
metadata:
name: k6-testrun-se
namespace: default
spec:
Other environment details (if applicable)
No response
Steps to reproduce the problem
Expected behaviour
Deployment should run with no error
Actual behaviour
Getting error
"no matches for kind "K6" in sigs.k8s.io/controller-runtime/pkg/internal/source.(*Kind[...]).Start.func1.1" even with TestRun usage
The text was updated successfully, but these errors were encountered: