Feature: Document `nextcloud.postgreSqlInitContainer` value

[lindhe]

Description of the change

The templates considers the value .Values.nextcloud.postgreSqlInitContainer.securityContext :

helm/charts/nextcloud/templates/deployment.yaml

Lines 320 to 323 in f184134

	{{- with .Values.nextcloud.postgreSqlInitContainer.securityContext }}
	securityContext:
	{{- toYaml . | nindent 12 }}
	{{- end }}

I suggest we document it along with all other values.

Benefits

Users know that this important value exists.

Possible drawbacks

Documentation is boring.

Additional information

I'm happy to implement this for you, just want to know that a contribution is welcome.

[jessebot]

Looks like it made it into the values.yaml so that's half the battle:

helm/charts/nextcloud/values.yaml

Lines 311 to 314 in 13ec7e6

	# Settings for the PostgreSQL init container
	postgreSqlInitContainer:
	# Set postgresql initContainer securityContext parameters. For example, you may need to define runAsNonRoot directive
	securityContext: {}

I agree with you though, that it should make it into the README as well. If you can, we'd love a PR for updating this section of the README to include that parameter:
https://github.com/nextcloud/helm/tree/main/charts/nextcloud#database-configurations

Putting it somewhere around here seems ideal:

helm/charts/nextcloud/README.md

Lines 247 to 259 in 13ec7e6

	| `postgresql.enabled` | Whether to use the PostgreSQL chart | `false` |
	| `postgresql.image.registry` | PostgreSQL image registry | `docker.io` |
	| `postgresql.image.repository` | PostgreSQL image repository | `bitnami/postgresql` |
	| `postgresql.image.tag` | PostgreSQL image tag | `15.4.0-debian-11-r10` |
	| `postgresql.global.postgresql.auth.database` | Database name to create | `nextcloud` |
	| `postgresql.global.postgresql.auth.username` | Database user to create | `nextcloud` |
	| `postgresql.global.postgresql.auth.password` | Password for the database | `changeme` |
	| `postgresql.global.postgresql.auth.existingSecret` | Name of existing secret to use for PostgreSQL credentials | `''` |
	| `postgresql.global.postgresql.auth.secretKeys.adminPasswordKey` | Name of key in existing secret to use for PostgreSQL admin password | `''` |
	| `postgresql.global.postgresql.auth.secretKeys.userPasswordKey` | Name of key in existing secret to use for PostgreSQL user password | `''` |
	| `postgresql.global.postgresql.auth.secretKeys.replicationPasswordKey` | Name of key in existing secret to use for PostgreSQL replication password | `''` |
	| `postgresql.primary.persistence.enabled` | Whether or not to use PVC on PostgreSQL primary | `false` |
	| `postgresql.primary.persistence.existingClaim` | Use an existing PVC for PostgreSQL primary | `nil` |