Skip to content

Conversation

@chrisseto
Copy link
Contributor

Prior to this commit the operator chart's declared permissions had grown out of sync with those declared by the operator itself. This commit re-synchronizes the permissions, adds in regression tests to prevent such drift from happening again, and releases the updated chart.

@chrisseto
Copy link
Contributor Author

Wait on redpanda-data/redpanda-operator#301 to be merged and for a release to be cut.

kind: Kustomization
resources:
# TODO: Move these links back to main and then to the tag in appVersion.
- https://raw.githubusercontent.com/redpanda-data/redpanda-operator/chris/p/correct-rbac/operator/config/rbac/leader-election-role/role.yaml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm assuming this will get updated after redpanda-data/redpanda-operator#301 merges

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep! That's the plan.

{
Verbs: []string{"get", "list", "patch", "update", "watch"},
APIGroups: []string{"cluster.redpanda.com"},
Resources: []string{"users"},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh gosh, I just now saw the differentiation here between

values.Scope == Namespace

and

values.Scope == Cluster

if you're adding this here (under Cluster) we'll likely want to do schemas as well. Then again is the Cluster scope intended to be for the v1 operator based on the bootup logic for the operator?

Either way I think that we'll want to either drop this (if it is solely for the v1 controller) or add in schemas as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed. To be on the safe side, I'm leaving the V2 permissions in V1 as they won't have an adverse affect if they're not installed or used AFAIK. Ideally, we'll eventually remove all the gating.

@chrisseto chrisseto force-pushed the chris/add-operator-permissions branch 2 times, most recently from 2f1f568 to 20ae4f6 Compare November 13, 2024 13:42
Prior to this commit the operator chart's declared permissions had grown
out of sync with those declared by the operator itself. This commit
re-synchronizes the permissions, adds in regression tests to prevent
such drift from happening again, and releases the updated chart.

Co-authored-by: Rafal Korepta <rafal.korepta@gmail.com>
@RafalKorepta
Copy link
Contributor

It's already merged in #1600

@chrisseto chrisseto deleted the chris/add-operator-permissions branch November 22, 2024 15:18
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.

4 participants