Powered by Zoomin Software. For more details please contactZoomin

MarkLogic® Server on Kubernetes

Security context

  • Last Updated: April 14, 2026
  • 1 minute read
    • MarkLogic Server
    • Documentation

Security context defines privilege and access control settings for a pod or container. By default, security context for containers is enabled with the runAsUser, runAsNonRoot, and allowPrivilegeEscalation settings. To configure these values for containers, set the containerSecurityContext in the values.yaml file or use the --set flag for Helm Charts and sample.yaml  for Operator. You can also add security context settings to the containerSecurityContext configuration. See Configure a Security Context for a Pod or Container for additional information.

This is the current configuration:

containerSecurityContext:
  enabled: true
  runAsUser: 1000
  runAsNonRoot: true
  allowPrivilegeEscalation: true

Warning:

This security context should not be modified. See Known issues and limitations.

TitleResults for “How to create a CRG?”Also Available inAlert