Closed kaiohenricunha closed 2 weeks ago
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Isn't there any workaround for this?
This Issue 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. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami/thanos latest
What is the problem this feature will solve?
The current configuration only allows Ruler to interact with recordings and alertings via configmap, a big no if a project is already running hundreds of records of PrometheusRules to manage Prometheus records and alerts.
What is the feature you are proposing to solve the problem?
Just like in the kube-prometheus-stack, using rulerSelector for discovering rules will make the overall experience much more easier to automate.
What alternatives have you considered?
Using the kube-prometheus-stack just to deploy the Thanos Ruler, which wouldn’t be the best option…