[bitnami/postgresql-ha] Helm chart templates field "enabled" in podSecurityContext of pgpool init container.

[caspereijkens]

Name and Version

bitnami/postgresql-ha

What architecture are you using?

None

What steps will reproduce the bug?

1. Enable .Values.pgpool.tls.enabled
2. That will activate

securityContext: {{- .Values.volumePermissions.podSecurityContext | toYaml | nindent 12 }}

In the pgpool deployment.
3. This leads to the field enabled being included in securityContext, which is of course not allowed by the Pod resource definition.

What is the expected behavior?

        securityContext:
          runAsGroup: 0
          runAsNonRoot: false
          runAsUser: 0
          seccompProfile:
            type: RuntimeDefault

What do you see instead?

        securityContext:
          **enabled: true**
          runAsGroup: 0
          runAsNonRoot: false
          runAsUser: 0
          seccompProfile:
            type: RuntimeDefault

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.