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

Thanos Multi-cluster deployment #166

Open
edenkoveshi opened this issue Dec 2, 2021 · 1 comment
Open

Thanos Multi-cluster deployment #166

edenkoveshi opened this issue Dec 2, 2021 · 1 comment

Comments

@edenkoveshi
Copy link

Describe the bug
So I'm following this: https://banzaicloud.com/docs/one-eye/thanos-operator/quickstarts/multicluster/ on a multi-namespace cluster
I would expect to see on the peer side 3 pods (or at least 3 containers):
Query, Rule and StoreAPI gateway to collect metrics from object storage
Although only 1 pod is set up with 1 container, for the query deployment
Using this with Prometheus operator and Prometheus sidecars, what I get is that the data is indeed uploaded to an object storage,
but I can query only the data of the Prometheus (that is shipped from the sidecar)

Steps to reproduce the issue:
Really just copy these YAMLs https://banzaicloud.com/docs/one-eye/thanos-operator/quickstarts/multicluster/

Expected behavior
Have a complete set-up of Query, Ruler and StoreAPI gateway

@edenkoveshi
Copy link
Author

Well, apparently I had to allow it to access my Grafana resources to make it work.
Any chance to fix that? This is really bad. GrafanaDatasource is completely unrelated and I should be able to choose not to reconcile it by the operator.

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

1 participant