Skip to content

K8s: configure role permissions #1817

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

K8s: configure role permissions #1817

wants to merge 2 commits into from

Conversation

kaitlynmichael
Copy link
Contributor

Copy link
Contributor

github-actions bot commented Jul 7, 2025

Copy link

@hassankh148 hassankh148 left a comment

Choose a reason for hiding this comment

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

One thing I would add, in addition to the requested changes - is mentioning that Admission would reject the request to configure an REAADB with rolesPermissions when either a Role or an ACL is missing, but ONLY on the MAIN cluster (the cluster in which the configuration is applied).

Comment on lines 163 to 178

```sh
kubectl get reaadb <reaadb-name>

NAME STATUS SPEC STATUS GLOBAL CONFIGURATIONS REDB LINKED REDBS
reaadb-boeing active Valid
```

4. Check the operator logs to confirm role permissions are applied:

```sh
kubectl logs -l name=redis-enterprise-operator
```

Look for log messages indicating "patching local BDB roles permissions" on each participating cluster.

Choose a reason for hiding this comment

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

Both of these are indeed an overkill.
I would suggest verifying that the local BDB has the roles_permissions field - i.e. the configuration has been propagated properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants