-
Notifications
You must be signed in to change notification settings - Fork 7
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
Remove label for old slo framework #393
Conversation
Can you link the sloth rules covering the prometheus-operator availability ? |
Well no because it does not exist yet |
Does it mean we'll lost slo on prometheus-operator when we merge that PR ? |
When we release it into the bundle yes but we are not in a rush to release |
Ok do we have a ticket to create the sloth rules ? |
Yes here giantswarm/roadmap#3318 (comment) |
I don't like the idea of releasing kps and waiting to release o11y-bundle because we can forget to wait. I'd prefer synchronizing PR removing old slo and PR adding sloth rules. |
Sure sure |
@marieroque I still need an approval :D |
Towards giantswarm/roadmap#3318
This PR removes the label used by the old slo framework in order to get rid of the old slo framework.
This will be turned into an availability slo for the prometheus operator in sloth-rules https://github.com/giantswarm/sloth-rules/pull/186