Skip to content

Docs for security_context_settings show container-level settings #2088

@erhhung

Description

@erhhung

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.

Bug Summary

The docs for security_context_settings show container-level only settings allowPrivilegeEscalation and capabilities, which do not get rendered into the Deployment templates for awx-web and awx-task because these settings are applied only at the pod level.

AWX Operator version

2.19.1

AWX version

24.6.1

Kubernetes platform

kubernetes

Kubernetes/Platform version

1.32

Modifications

no

Steps to reproduce

This gets rendered at the pod-level:

spec:
  security_context_settings:
    runAsUser: 0
    runAsGroup: 0
    fsGroup: 2000
    fsGroupChangePolicy: OnRootMismatch

This (from the docs) gets rendered no where:

spec:
  security_context_settings:
    allowPrivilegeEscalation: false
    capabilities:
      drop:
        - ALL

Expected results

Fix the example in the docs and explicitly state whether security_context_settings (and postgres_security_context_settings) apply at the pod-level or at the container-level.

Actual results

spec.security_context_settings.allowPrivilegeEscalation and spec.security_context_settings.capabilities do not get applied to container-level securityContext.

Additional information

No response

Operator Logs

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions