Skip to content
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

Add usage collection report #525

Open
yorugac opened this issue Feb 2, 2025 · 1 comment
Open

Add usage collection report #525

yorugac opened this issue Feb 2, 2025 · 1 comment
Labels
enhancement New feature or request meta Related to high-level configuration of k6-operator.

Comments

@yorugac
Copy link
Collaborator

yorugac commented Feb 2, 2025

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:

  1. Currently k6-operator version is not exposed in the code - that will need to be changed here.
  2. 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.
  3. 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

@yorugac yorugac added enhancement New feature or request meta Related to high-level configuration of k6-operator. labels Feb 2, 2025
@yorugac
Copy link
Collaborator Author

yorugac commented Feb 3, 2025

Pre-install hook for Helm chart might be of use here too:
https://helm.sh/docs/topics/charts_hooks/

But it'd be a pretty separate flow from the main app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request meta Related to high-level configuration of k6-operator.
Projects
None yet
Development

No branches or pull requests

1 participant