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

Difference between the Bitnami Helm Chart and Kube-Thanos #316

Open
amrap030 opened this issue Jan 23, 2024 · 1 comment
Open

Difference between the Bitnami Helm Chart and Kube-Thanos #316

amrap030 opened this issue Jan 23, 2024 · 1 comment

Comments

@amrap030
Copy link

Hello together,

I would like to know what is the difference between the Bitname Helm Chart of Thanos (https://artifacthub.io/packages/helm/bitnami/thanos) and Kube-Thanos?

At first, I installed Thanos via the manifests directory of this repository (https://github.com/thanos-io/kube-thanos/tree/main/manifests) and everything worked fine. However, it seems to deploy not every component of Thanos. I cannot see the compactor and the query frontent for example.

Then I installed Thanos via the Helm Chart with the compactor and the query frontend as well, but the Helm Chart completely broke my kubernetes worker nodes because it ran into a OOM problem and extremely high load. In addition, the deployment looked a little bit different for the receiver for example. With kube-thanos the receiver is divided into in ingestor and a router and with the Helm Chart there is only one receiver component deployed.

I hope someone can help me, I would like to deploy all components including the compactor and query frontend without crashing my cluster.

@metalmatze
Copy link
Contributor

kube-thanos is based on jsonnet and extends kube-prometheus. As part of kube-prometheus, the Prometheus Operator gets deployed, which is most likely the pieces you're missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants