Kubernetes Security Context#

Overview#

The dify-helm chart applies Kubernetes security contexts at both the pod level (podSecurityContext) and the container level (containerSecurityContext) for each component. Configuration is entirely driven by values.yaml; all deployment templates conditionally render the security context only when the corresponding value is non-empty or has enabled: true.

Per-Component Defaults#

Sources: 1 2 3 4 5 6 7 8

Key observations:

• api, worker, and beat run as UID/GID 1001 (standard non-root application user).
• proxy uses UID/GID 101, matching the default nginx user ID. The fsGroupChangePolicy: "Always" forces recursive ownership change on mounted volumes 9.
• web, sandbox, ssrfProxy, and pluginDaemon ship with empty objects — no security context is applied by default, and non-root/privilege configuration must be added explicitly by the operator.

Template Pattern#

Every deployment template follows the same conditional rendering pattern:

• Pod-level: the securityContext block is emitted only when .Values.<component>.podSecurityContext is non-empty (truthy). For components with an enabled key, that key is stripped before rendering via Helm's omit function. See sandbox-deployment.yaml lines 61–64 for a representative example.
• Container-level: same pattern — emitted only when .Values.<component>.containerSecurityContext is non-empty. See sandbox-deployment.yaml lines 92–95.

This pattern is identical across all eight deployment templates (api, worker, beat, proxy, web, sandbox, ssrfProxy, pluginDaemon).

Configuring Non-Root Execution (sandbox and others)#

For components with no defaults (sandbox, web, ssrfProxy, pluginDaemon), operators must supply the security context explicitly. A typical non-root configuration in values.yaml would be:

sandbox:
  podSecurityContext:
    runAsNonRoot: true
    runAsUser: 1000
    fsGroup: 1000
  containerSecurityContext:
    runAsNonRoot: true
    runAsUser: 1000
    allowPrivilegeEscalation: false
    readOnlyRootFilesystem: true

There are no chart-level guard rails for these components — if neither podSecurityContext nor containerSecurityContext is set, the pod inherits the container image's default (which may be root). See the sandbox values and sandbox deployment template for the exact conditionals.

Source References#