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

[kube-prometheus-stack] Decomposition #510

Closed
vladarts opened this issue Dec 21, 2020 · 4 comments
Closed

[kube-prometheus-stack] Decomposition #510

vladarts opened this issue Dec 21, 2020 · 4 comments
Labels
enhancement New feature or request lifecycle/stale

Comments

@vladarts
Copy link
Contributor

Hi!

Current implementation of kube-prometheus-stack is a monolith solution which makes possible to install prometheus components only once. If you need to have multiple Prometheus installations in cluster you can:

  1. Install this chart one more time but you have to manually disable all components before which makes configuration more complex.
  2. Install required components manually but it is less useful because kube-prometheus-stack already has all required resources for components work (services, ingresses, servicemonitors).

I can see some possible solutions:

  1. Move prometheus, alertmanager and potentially thanos rule templates in separate helm charts and install them as dependencies.
  2. Add an option to disable by default installation of all components.

What do you think about it?
Thanks!

@vladarts vladarts added the enhancement New feature or request label Dec 21, 2020
@scottrigby
Copy link
Member

In general this was part of the plan when we moved and renamed the chart, to simplify the charts where possible: phase 2 after moving them as-is. See prometheus-community/community#28 (comment)

@vladarts
Copy link
Contributor Author

Do you plan to finish this activity and if yes - do you have any estimations?

@stale
Copy link

stale bot commented Jan 21, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale
Copy link

stale bot commented Feb 4, 2021

This issue is being automatically closed due to inactivity.

@stale stale bot closed this as completed Feb 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request lifecycle/stale
Projects
None yet
Development

No branches or pull requests

2 participants