Repository navigation
Update rollout operator usage - #673
Merged
Merged
Conversation
timonegk
force-pushed
the
update-rollout-operator
branch
3 times, most recently
from
September 25, 2026 14:01
d120de4 to
76571c1
Compare
nschad
approved these changes
Sep 25, 2026
timonegk
force-pushed
the
update-rollout-operator
branch
from
September 28, 2026 07:41
af69b10 to
d2fecb8
Compare
nschad
approved these changes
Sep 29, 2026
Signed-off-by: Timon Engelke <timon.engelke@inovex.de>
Signed-off-by: Timon Engelke <timon.engelke@inovex.de>
Signed-off-by: Timon Engelke <timon.engelke@inovex.de>
Signed-off-by: Timon Engelke <timon.engelke@inovex.de>
Contributor
Author
|
rebased |
timonegk
force-pushed
the
update-rollout-operator
branch
from
September 29, 2026 13:15
74ee8c0 to
eaa3ef0
Compare
kd7lxl
approved these changes
Oct 7, 2026
| It is sufficient to set these settings on the querier using `querier.extraArgs`. Set `distributor.sharding-strategy` to `default` and `distributor.shard-by-all-labels` to `"true"` there. | ||
| Warning: This may increase resource usage of the queriers. | ||
|
|
||
| To get the rollout-operator running, you will have to install its CRDs. Due to Helm's CRD handling, you have to apply [these manifests](https://github.com/grafana/helm-charts/tree/main/charts/rollout-operator/charts/crds/crds) manually |
Collaborator
There was a problem hiding this comment.
I would prefer to see instructions for deploying rollout-operator independently. This way helm can install the CRDs. An operator in a subchart is messy because of this CRDs issue, and also because you generally only want one, while you may have several cortex instances in a cluster. Without instructions for a standalone rollout-operator installation, users are left to choose which instance of cortex they want to own rollout-operator.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does:
Follow-up on #668. These are some fixes regarding the rollout operator.
Chart.yamlso that users can set custom valuesChecklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX],[DEPENDENCY]