Skip to content
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

Update for openshift OperatorHub Note: Known Limitation #123

Open
hmarrao opened this issue Apr 18, 2024 · 2 comments
Open

Update for openshift OperatorHub Note: Known Limitation #123

hmarrao opened this issue Apr 18, 2024 · 2 comments
Assignees

Comments

@hmarrao
Copy link

hmarrao commented Apr 18, 2024

On the note:

Known Limitation - The automatic use of the security constraint is limited. The Redis Enterprise must be named rec for the constraint to be used automatically. Use the cluster name rec when deploying with the OperatorHub

one may add:

or ensure that rec yaml is using the proper rec service account by setting "rec.spec.serviceAccountName: rec" and "rec.spec.createServiceAccount: false" into your yaml definition.

If you require a different name, you must grant the SCC to the project namespace.

@mich-elle-luna
Copy link
Collaborator

mich-elle-luna commented Apr 18, 2024

Hi,

Thank you for this suggestion, are you referring to this page? https://redis.io/docs/latest/operate/kubernetes/deployment/openshift/openshift-operatorhub/
Just want to be sure we update the right content.

-Michelle

@hmarrao
Copy link
Author

hmarrao commented Apr 19, 2024

Hello, Hope you are dogin well ...

yes that the page yes!!!

... thx ...

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

No branches or pull requests

3 participants