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
K8s cluster domain is set to cluster.local by default. However, our K8s cluster has changed this config to others which caused the operator not to be able to find the service of an object whose kind is K6. Hence, the StartJob can not be started as expected.
The code to find the K8s service is hardcoded in the StartJobs function.
Not able to find the service via DNS record due to hardcoded URL
Operator Log:
2023-10-31T10:21:07Z ERROR controllers.K6 failed to get status from k6-sample-service
github.com/grafana/k6-operator/controllers.isServiceReady
/workspace/controllers/k6_start.go:23
github.com/grafana/k6-operator/controllers.StartJobs
The text was updated successfully, but these errors were encountered:
@nhatnam1198, this issue got a bit lost in the torrent of others, but it's actually a duplicate of an older issue #233 which was recently fixed. Please try the latest version of k6-operator: it should work. If it doesn't, please re-open with additional details. Thanks.
Brief summary
K8s cluster domain is set to
cluster.local
by default. However, our K8s cluster has changed this config to others which caused the operator not to be able to find the service of an object whose kind isK6
. Hence, theStartJob
can not be started as expected.The code to find the K8s service is hardcoded in the
StartJobs
function.k6-operator/controllers/k6_start.go
Line 20 in 7ce63b1
k6-operator version or image
https://github.com/grafana/k6-operator/releases/tag/v0.0.11
K6 YAML
Other environment details (if applicable)
No response
Steps to reproduce the problem
Use
make deploy
as mentioned in README.mdExpected behaviour
K6 Operator is able to find the required service
Actual behaviour
Not able to find the service via DNS record due to hardcoded URL
Operator Log:
The text was updated successfully, but these errors were encountered: