Skip to content

Update rollout operator usage - #673

Open
timonegk wants to merge 4 commits into
cortexproject:masterfrom
timonegk:update-rollout-operator
Open

timonegk wants to merge 4 commits into
cortexproject:masterfrom
timonegk:update-rollout-operator

Conversation

@timonegk

Copy link
Copy Markdown
Contributor

What this PR does:
Follow-up on #668. These are some fixes regarding the rollout operator.

  • set the alias in Chart.yaml so that users can set custom values
  • CRDs are required to run the operator, so this adds installation instructions for them and drops disabling the CRDs
  • Set the security context on the rollout operator (same values as used by Grafana)

Checklist

  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX], [DEPENDENCY]

@timonegk
timonegk force-pushed the update-rollout-operator branch 3 times, most recently from d120de4 to 76571c1 Compare September 25, 2026 14:01
@timonegk
timonegk force-pushed the update-rollout-operator branch from af69b10 to d2fecb8 Compare September 28, 2026 07:41
@nschad
nschad requested a review from kd7lxl September 29, 2026 08:25
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>
@timonegk

Copy link
Copy Markdown
Contributor Author

rebased

@timonegk
timonegk force-pushed the update-rollout-operator branch from 74ee8c0 to eaa3ef0 Compare September 29, 2026 13:15

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants