Closed langesven closed 1 year ago
Hi @langesven :wave: Thanks for the report and good timing actually: I'm just preparing PR to update deps because of the CI issue - might as well update client-go.
I assume you meant this one in k9s: https://github.com/derailed/k9s/issues/2055 and https://github.com/derailed/k9s/pull/2075 - thanks for the pointer! It looks like 0.26.4 should work as well 0.27.0+ :thinking:
For the record. Sadly, this case is not repeatable with kind cluster :disappointed: CI job here is successful: https://github.com/grafana/k6-operator/actions/runs/6487684065/job/17618588971
Yes I think it's not something that really happens on a vanilla cluster but actually needs a bit of garbage floating around 😅
If you have a preliminary image I'll gladly give it a go in the cluster where I encountered this issue
@langesven, the image with dependency updates can be reached with:
ghcr.io/grafana/k6-operator:30577947ac70e51717e5e1ca4b1c84c84dceb11d
Preliminarily it should work though I haven't tested all the scenarios yet. If you could try it with 1.27, that'd be great!
Thanks! This image works on my cluster, I was able to run the operator and start a test etc 😄 I probably run very basic things right now but compared to it not starting at all before I consider it success 😁
:tada: Great to hear! Many thanks for checking @langesven :smile: I'll test the update a bit more and merge it in, hopefully this week.
Brief summary
Hi,
we've recently been planning on giving the
k6-operator
a go so I set it up yesterday in our AWS EKS cluster (v1.27.5-eks-43840fb
) but the manager fails to start with the below output:This is something I've seen before when upgrading from K8s 1.26 to K8s 1.27 for example
k9s
binary was showing the same behaviour until updated.I am assuming this is related to the version of the k8s-client library used in go.
k6-operator version or image
ghcr.io/grafana/k6-operator:controller-v0.0.11rc3
K6 YAML
Stock
bundle.yaml
from https://github.com/grafana/k6-operator#bundle-deploymentOther environment details (if applicable)
No response
Steps to reproduce the problem
Expected behaviour
Actual behaviour
CrashLoopBackoff
due to the error pasted above