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

Per-cluster Kosmoo vs multiple-clusters-per-OpenStack #106

Open
MPV opened this issue May 18, 2022 · 3 comments
Open

Per-cluster Kosmoo vs multiple-clusters-per-OpenStack #106

MPV opened this issue May 18, 2022 · 3 comments

Comments

@MPV
Copy link

MPV commented May 18, 2022

Hi,
In what way (cardinality) do you deploy and run Kosmoo across clusters and OpenStack environments/tenants?

I'm asking since we've initially set it up to run "one per Kubernetes cluster", but since we have multiple Kubernetes clusters running in the same OpenStack region and tenant, it causes us to get the same metrics (and thus alerts) from multiple clusters (for example broken load balancers/servers when erroring in provisioning state).

@tobiasgiese
Copy link
Member

tobiasgiese commented Jun 1, 2022

Hi @MPV.

We are also using Kosmoo to run as "one per Kubernetes cluster". But the difference in our provisioning/operation is, that we're using one Openstack project (i.e., tenant) per cluster. So we have only metrics for this particular cluster.

Edit: but maybe it's enough for your use-case to use the name label in the kosmoo metrics, which describes the OpenStack resource name. Or we could add a feature to filter for resource names that matches a specific value.

@MPV
Copy link
Author

MPV commented May 10, 2023

@tobiasgiese Could you take a look at #121? 🙏

@tobiasgiese
Copy link
Member

@MPV sorry, I haven't reviewed the PR because it's still a draft. But let me start with the review :)

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