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
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Hi @carrodher , I've tested my changes with minikube locally. New statefulset works fine as a cluster.
Regarding the VIB test, how to achieve 2 different sets of env for testing?
Since it should test both cases: tempo.deploymentMode=microservices and tempo.deploymentMode=scalingMonolithic
Thank you for opening this issue and submitting the associated Pull Request. Our team will review it and provide feedback. Please ask about testing scenarios in the PR itself. The reviewers will help you there since they have the whole context.
Once the PR is merged, the issue will automatically close.
Name and Version
bitnami/grafana-tempo
What is the problem this feature will solve?
Support new type of Tempo running mode: https://grafana.com/docs/tempo/latest/setup/deployment/#scaling-monolithic-mode
It would help to maintain a reasonable size of cluster handling small to medium volumes of incoming traces
What is the feature you are proposing to solve the problem?
Create a statefulset, in which pods are started with arg
-target=scalable-single-binary
. All pods can stay in the same gossip ring as a clusterThe text was updated successfully, but these errors were encountered: