From 15c862fcb5316cedd750291eb0ab10c96004e2bf Mon Sep 17 00:00:00 2001 From: Eric Paulsen Date: Tue, 14 Feb 2023 12:04:16 -0500 Subject: [PATCH] fix: set Coder read-only fs to null (#6207) * fix: set Coder read-only fs to null * chore: readme fixes * chore: readme fixes v2 --- helm/values.yaml | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/helm/values.yaml b/helm/values.yaml index 5d8fd84a26..f6fa30239f 100644 --- a/helm/values.yaml +++ b/helm/values.yaml @@ -58,16 +58,15 @@ coder: # runs as an unprivileged user. If setting runAsUser to 0 (root), this # will need to be set to false. runAsNonRoot: true - # coder.securityContext.runAsUser -- Sets the user id of the pod. + # coder.securityContext.runAsUser -- Sets the user id of the container. # For security reasons, we recommend using a non-root user. runAsUser: 1000 - # coder.securityContext.runAsGroup -- Sets the group id of the pod. + # coder.securityContext.runAsGroup -- Sets the group id of the container. # For security reasons, we recommend using a non-root group. runAsGroup: 1000 # coder.securityContext.readOnlyRootFilesystem -- Mounts the container's - # root filesystem as read-only. It is recommended to leave this setting - # enabled in production. This will override the same setting in the pod - readOnlyRootFilesystem: true + # root filesystem as read-only. + readOnlyRootFilesystem: null # coder.securityContext.seccompProfile -- Sets the seccomp profile for # the coder container. seccompProfile: