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

cyctl telemetry flag #364

Closed
KaradzaJuraj opened this issue Jun 25, 2024 · 4 comments · Fixed by #412
Closed

cyctl telemetry flag #364

KaradzaJuraj opened this issue Jun 25, 2024 · 4 comments · Fixed by #412
Assignees
Labels
cyctl Issues related to the CLI good first issue Good for newcomers

Comments

@KaradzaJuraj
Copy link
Collaborator

Problem

When installing Cyclops with kubectl and the install manifests, you have the option to turn off telemetry. But when installing Cyclops with cyctl and the init command, this option does not exist.

Solution

Implement a —-disable-telemetry flag to disable telemetry when installing Cyclops via cyctl.

The command should look like the following:

cyctl init —-disable-telemetry
@KaradzaJuraj KaradzaJuraj added good first issue Good for newcomers cyctl Issues related to the CLI labels Jun 25, 2024
@thebigbone
Copy link
Contributor

How is telemetry disabled with kubectl?

@KaradzaJuraj
Copy link
Collaborator Author

KaradzaJuraj commented Jun 27, 2024

You need to add the environment variable to cyclops-ctrl deployment.
You can find details in our documentation here.

@thebigbone
Copy link
Contributor

You need to add the environment variable to cyclops-ctrl deployment. You can find details in our documentation here.

Got it. So, the most simple solution is to inject this environment variable while running init. I will try to implement it.

@KaradzaJuraj
Copy link
Collaborator Author

Yes! I'll assign you to the issue then 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cyctl Issues related to the CLI good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants