[Bug]: Documentation still reports pod security policies

[gbartolini]

Is there an existing issue already for this bug?

• I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

• I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

• I have read the troubleshooting guide and I think this is a new bug.

Contact Details

No response

Version

1.24.0

What version of Kubernetes are you using?

1.31

What is your Kubernetes environment?

Self-managed: kind (evaluation)

How did you install the operator?

YAML manifest

What happened?

The security page still reports pod security policies - which have been deprecated. See: https://cloudnative-pg.io/documentation/current/security/#pod-security-policies

We should change it into security contexts.

I exported the ones for the postgres container:

    securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
        - ALL
      privileged: false
      readOnlyRootFilesystem: true
      runAsNonRoot: true
      seccompProfile:
        type: RuntimeDefault

Cluster resource

No response

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[sharifmshaker]

I would be interested to pick this up as a first issue. I have work for this in a PR #6303, but am not sure if I need this issue as a ticket first as described in the contributor doc. I did not see a ticket for the work here CloudNativePG operator development and thought maybe one needed to be created first.