You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encounter an issue with k6-operator which is not able to fetch status of his runners, on a cluster which do not use cluster.local (this is uncommon config but perfectly valid) because of this hardcoded code
I think ideally, it'd be preferable to switch to using service.namespace format instead of the full domain as now, then the whole question about domains will disappear. There were several different cases raised around networking in the operator which sometimes seemed contradictory to each other, so there's an umbrella issue meant to hopefully resolve all of them at once: #186
Brief summary
I encounter an issue with k6-operator which is not able to fetch status of his runners, on a cluster which do not use
cluster.local
(this is uncommon config but perfectly valid) because of this hardcoded codek6-operator/controllers/k6_start.go
Line 20 in 9a06624
What could be the way to fix this ? define some variable somewhere ? using
.svc
instead of.svc.cluster.local
? what do you prefer ?as a workaround, i changed on which the cluster i deploy but could be great to fix this.
k6-operator version or image
latest
K6 YAML
Other environment details (if applicable)
No response
Steps to reproduce the problem
deploy some K6 resources
Expected behaviour
runners can be joined and status fetched
Actual behaviour
runners can't be joined and nothing finish
The text was updated successfully, but these errors were encountered: