[stable/rabbitmq-ha] Fix securityContext for group ID file system permissions (#12063)

The new `fsGroup` flag allows to enable the group id at a file-system level.
This is useful to prevent permission errors, especially on clusters with the following Kubernetes cluster flag not set to `RunAsGroup=true`.

Signed-off-by: Samuel Cordeiro <cordeiro.samuel@gmail.com>
This commit is contained in:
sigmascord
2019-03-11 07:49:33 -07:00
committed by Kubernetes Prow Robot
parent e8fbe86e9c
commit 897a8bba3d
3 changed files with 3 additions and 1 deletions
+1 -1
View File
@@ -1,7 +1,7 @@
name: rabbitmq-ha
apiVersion: v1
appVersion: 3.7.8
version: 1.21.0
version: 1.21.1
description: Highly available RabbitMQ cluster, the open source message broker
software that implements the Advanced Message Queuing Protocol (AMQP).
keywords:
+1
View File
@@ -138,6 +138,7 @@ and their default values.
| `rbac.create` | If true, create & use RBAC resources | `true` |
| `replicaCount` | Number of replica | `3` |
| `resources` | CPU/Memory resource requests/limits | `{}` |
| `securityContext.fsGroup` | Group ID for the container's volumes | `101` |
| `securityContext.runAsGroup` | Group ID for the container | `101` |
| `securityContext.runAsNonRoot` | Enforce non-root user ID for the container | `true` |
| `securityContext.runAsUser` | User ID for the container | `100` |
+1
View File
@@ -437,6 +437,7 @@ existingSecret: ""
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
##
securityContext:
fsGroup: 101
runAsGroup: 101
runAsNonRoot: true
runAsUser: 100