Skip to content

Add security context for crdHook to enable security policy compliance#1950

Open
qlevasseur-genetec wants to merge 1 commit intoAltinity:0.27.0from
qlevasseur-genetec:ql/crdhook-security-context
Open

Add security context for crdHook to enable security policy compliance#1950
qlevasseur-genetec wants to merge 1 commit intoAltinity:0.27.0from
qlevasseur-genetec:ql/crdhook-security-context

Conversation

@qlevasseur-genetec
Copy link
Copy Markdown

Adds crdHook.containerSecurityContext option to configure container security context for the CRD installation job, enabling compliance with security policies (e.g., Kyverno).

Changes

  • values.yaml: Added crdHook.containerSecurityContext configuration option
  • templates/hooks/crd-install-job.yaml: Template now applies the security context to the container
  • values.schema.json: Added missing crdHook section with all its properties

Example usage

  crdHook:
    containerSecurityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
          - ALL
      runAsNonRoot: true
      seccompProfile:
        type: RuntimeDefault

@Slach Slach changed the base branch from master to 0.27.0 March 30, 2026 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants