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
The endpoint for usage reports is simple and can be easily sent on the start of the k6-operator. But there are open questions:
Currently k6-operator version is not exposed in the code - that will need to be changed here.
OS and arch make no sense for k6-operator. Confirm if there's anything else that makes sense to use instead, like getting Kubernetes version.
k6-studio relies on "installation ID" written to the file system: https://github.com/grafana/k6-studio/blob/14f94da52ba84f0847df66a30005c1244032f680/src/usageReport.ts#L12
This cannot be used by k6-operator without volumes which is an overkill here. But without persistence, it'd be impossible to distinguish between installation and restart of the app. emptyDir volume can handle restart in-place but not the pod's rescheduling 😕
Opt-out should probably be done the same as in k6 and k6-studio, with a CLI argument.
Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered:
Feature Description
To improve decision-making, add installation collection, similar to what was done for k6-studio:
https://grafana.com/docs/k6-studio/set-up/usage-collection/
Suggested Solution (optional)
The endpoint for usage reports is simple and can be easily sent on the start of the k6-operator. But there are open questions:
https://github.com/grafana/k6-studio/blob/14f94da52ba84f0847df66a30005c1244032f680/src/usageReport.ts#L12
This cannot be used by k6-operator without volumes which is an overkill here. But without persistence, it'd be impossible to distinguish between installation and restart of the app.
emptyDir
volume can handle restart in-place but not the pod's rescheduling 😕Opt-out should probably be done the same as in k6 and k6-studio, with a CLI argument.
Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered: