Skip to content

Allow disabling Posthog from helm #1014

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

Closed
Nastaliss opened this issue May 26, 2025 · 1 comment
Closed

Allow disabling Posthog from helm #1014

Nastaliss opened this issue May 26, 2025 · 1 comment
Labels
feature add a new feature triage

Comments

@Nastaliss
Copy link

Feature Request

I'd like to disable the Posthog url forwarding by default, as I do not (yet) use this service and would like to make the setup process as straightforward as possible.

Describe the solution you'd like
Add a .Values.posthog.enabled key to the value.yaml file and set it to true by default, this way no breaking change is introduced.
Disable the k8s resources if set to false

Describe alternatives you've considered
/

Discovery, Documentation, Adoption, Migration Strategy
Update the readme accordingly

Do you want to work on it through a Pull Request?
#1013

@Nastaliss Nastaliss added feature add a new feature triage labels May 26, 2025
@Nastaliss Nastaliss changed the title Allow disabling Posthog from kubernetes Allow disabling Posthog from helm May 26, 2025
@Nastaliss
Copy link
Author

Just realized that setting both ingress.enabled and ingressAssets.enabled to false will have the same effect.
It was not clear that disabling ingress would also disable the svc (and therefore disable the whole component).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature add a new feature triage
Projects
Status: Done
Development

No branches or pull requests

1 participant