-
Notifications
You must be signed in to change notification settings - Fork 232
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
Conversation
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.
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).
|
||
```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. |
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.
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.
Co-authored-by: hassankh148 <[email protected]>
* K8s: Yellow Submarine release notes (#1819) * 7.22.0-15 release notes * supported distro update * review feedback * K8s: configure role permissions (#1817) * configure role permissions * Apply suggestions from code review Co-authored-by: hassankh148 <[email protected]> * review feedback --------- Co-authored-by: hassankh148 <[email protected]> * K8s: helm upgrade changes (#1640) * helm upgrade changes * add helm info to upgrade pages * add migration section * update prereq * review edits --------- Co-authored-by: hassankh148 <[email protected]>
DOC-5442