-
Notifications
You must be signed in to change notification settings - Fork 363
Add a new mimir.alerts.kubernetes component #3448
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
base: main
Are you sure you want to change the base?
Add a new mimir.alerts.kubernetes component #3448
Conversation
// TODO: Upstream this change prior to merging the mimir.alerts.kubernetes component to main. | ||
replace github.com/prometheus-operator/prometheus-operator => github.com/ptodev/prometheus-operator v0.0.0-20250425071154-e2ee3c49b414 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will need to merge a PR upstream before I merge this feature.
46e4b8d
to
9a02eae
Compare
9a02eae
to
ca15a30
Compare
💻 Deploy preview available: |
d9f76dd
to
74de2da
Compare
2de59c8
to
cb30ab7
Compare
hi! we would interested in using this - what's the plan to merge it ? |
Hi @vladst3f! I'm still hopeful that this can go into the next Alloy release. However, I had a lot of trouble updating the go.mod file last time I tried to update the PR. There was a dependency which another one of Alloy's dependencies wanted on the latest version but other dependencies weren't compatible with the latest version. I might need to fork some dependencies in order to merge the PR. |
PR Description
Which issue(s) this PR fixes
Fixes #504
Notes to the Reviewer
PR Checklist