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.

Sign up for GitHub

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

Jump to bottom

Add securityContext and fix rabbitMQ cookie #232

Open
viktoriaas opened this issue Mar 18, 2022 · 0 comments
Open

Add securityContext and fix rabbitMQ cookie #232

viktoriaas opened this issue Mar 18, 2022 · 0 comments

Comments

@viktoriaas
Copy link
Contributor

Issue introduces 2 problems together with a PR solving them.

  1. Clusters with security policy enabled often forbid the usage of root. Therefore it is necessary to add optional securityContext to all deployments and to wes ConfigMap.

  2. If rabbitMQ deployment is restarted (e.g. due to cluster failure) rabbitMQ cookie has incorrect permissions after restart ( rw-rw---- instead of rw-------). This is solved by chmod in main container before calling rabbitmq.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@viktoriaas