-
Notifications
You must be signed in to change notification settings - Fork 631
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
Will there be a new helm chart since the acquisition? #1983
Comments
Hi @nabadger sorry for the inconvenience and thanks for the patience.
Yes definitely
Also yes we will do our best to have a migration path that causes minimal disruption We are in the process of merging the repos right now and are aiming to have all this complete by mid-august. This will be when we release Pyroscope 1.0. We've merged them internally (we run the merged version in Grafana Cloud) and are working through the logistics of how we can bring this merged version into the OSS world with minimal disruption to existing Phlare and Pyroscope. In the meantime, if you want to reach out on the #pyroscope channel in the Grafana slack or DM happy to discuss your orgs situation in more detail and help you make the decision on where / when to get started |
Awesome, thanks for the quick reply :) |
Any new updates on when the 1.0 release will be happening? |
Aiming for tomorrow! |
Hi,
Currently the helm chart is available at https://github.com/pyroscope-io/helm-chart
I'm wondering if there are any plans to change this to be more inline with existing grafana helm charts?
If so, do you imagine there would be a migration path available? We're wondering whether to move forward with pyroscope-io or whether to hold-off and wait for any changes in this area (given it's a recent acquisition).
Thanks
The text was updated successfully, but these errors were encountered: