-
Notifications
You must be signed in to change notification settings - Fork 245
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
mimir.rules.kubernetes: Add warning about clustering to docs #648
Conversation
f225be0
to
dea0579
Compare
The component doesn't support running in clustered mode. When multiple clustered Alloy instances run the component, they will end up conflicting with each other making API requests to the Mimir ruler. Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
dea0579
to
52c887c
Compare
@@ -24,6 +24,12 @@ in Kubernetes in order for {{< param "PRODUCT_NAME" >}} to access it via the Kub | |||
[Role-based access control (RBAC)]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/ | |||
{{< /admonition >}} | |||
|
|||
{{< admonition type="warning" >}} | |||
This component does not support [clustered mode][] and must be run in a separate single-instance deployment of {{< param "PRODUCT_NAME" >}}. |
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.
Do we want to include a brief explanation of what the issue is if you run it in clustered mode anyway to drive home that you really shouldn't?
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.
Good idea. Will update
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.
Fixed in c0cb0e4
Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
The component doesn't support running in clustered mode. When multiple clustered Alloy instances run the component, they will end up conflicting with each other making API requests to the Mimir ruler. Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> (cherry picked from commit 321df4c)
…652) The component doesn't support running in clustered mode. When multiple clustered Alloy instances run the component, they will end up conflicting with each other making API requests to the Mimir ruler. (cherry picked from commit 321df4c) Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
…#648) The component doesn't support running in clustered mode. When multiple clustered Alloy instances run the component, they will end up conflicting with each other making API requests to the Mimir ruler. Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
PR Description
The component doesn't support running in clustered mode. When multiple clustered Alloy instances run the component, they will end up conflicting with each other making API requests to the Mimir ruler.
Which issue(s) this PR fixes
N/A
Notes to the Reviewer
N/A
PR Checklist