From f6816df5f348edb32ecbd3353fe0b74a71381efe Mon Sep 17 00:00:00 2001 From: Jesse Hitch Date: Sun, 23 Apr 2023 22:24:53 +0200 Subject: [PATCH] remove note about default setting container securityContext --- charts/nextcloud/README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/charts/nextcloud/README.md b/charts/nextcloud/README.md index 9fe563f5..4ec5b05b 100644 --- a/charts/nextcloud/README.md +++ b/charts/nextcloud/README.md @@ -428,6 +428,4 @@ These are all the [securityContext](https://kubernetes.io/docs/reference/generat | `cronjob.securityContext.runAsNonRoot` | Optional security context for cronjob | | `nextcloud.podSecurityContext` | Optional security context for the NextCloud pod (applies to all containers in the pod) | -For the container, by default, only the `nextcloud.securityContext.runAsUser` and `nextcloud.securityContext.runAsGroup` for the nextcloud container are set, and the UID defaults to `33`, which is the UID of the `www-data` user. If you're using a nextcloud image with Alpine as the base, set this to `82`, the `www-data` user on alpine. - -For the pod, `nextcloud.podSecurityContext.fsGroup` is set to `33` by default. You should set this to `82` if you're using an alpine image. See more about how this special option works [here](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#podsecuritycontext-v1-core). +For the pod, `nextcloud.podSecurityContext.fsGroup` is set to `33` (`www-data` on the container) by default. You should set this to `82` if you're using an alpine nextcloud image. See more about how this special option works [here](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#podsecuritycontext-v1-core).