-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[bitnami/grafana-tempo] support new deployment mode: scaling-monolithic #31028
base: main
Are you sure you want to change the base?
Conversation
567ad9c
to
ce0e7fe
Compare
Signed-off-by: Zhang Xin <[email protected]>
51d6560
to
d8fc985
Compare
Signed-off-by: Bitnami Containers <[email protected]>
Signed-off-by: Bitnami Containers <[email protected]>
Thank you for this significant contribution, @rim99! The PR is currently in draft status. Please inform us when it's ready for testing and review. Thanks once more! |
Hi @jotamartos @migruiz4 , 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:
|
This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution. |
Hello, just a reminder that this PR is ready for review |
Description of the change
This change provides a new way of deployment:
scaling-monolithic
.If toggle
.Values.tempo.deploymentMode
, which is "microservices" by default, is set as "scalingMonolithic", single statefulset will be created. Each pod conatins all functions of components: distributor, ingester, query-frontend, querier, metrics-generator and compactor.Benefits
It helps to maintain a reasonable size of cluster handling small to medium volumes of incoming traces.
Possible drawbacks
Applicable issues
Additional information
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm