Add envFrom support to Postgresql spec

[annielzy]

Adds top-level spec.envFrom support for Postgresql resources, allowing the Spilo container to populate environment variables from ConfigMaps and Secrets using standard Kubernetes EnvFromSource entries.

Changes:

• Add EnvFrom []v1.EnvFromSource to PostgresSpec.
• Pass spec.envFrom into the generated Postgres container.
• Update deepcopy and PostgreSQL CRD schemas.
• Add tests covering StatefulSet updates and container generation with envFrom.

[FxKu]

Thanks @annielzy. Have you tried using the global pod_environment_configmap or pod_environment_secretoptions? Or do you really need to mount extra secrets / configmap locally per database resource?

[annielzy]

Thanks @annielzy. Have you tried using the global pod_environment_configmap or pod_environment_secretoptions? Or do you really need to mount extra secrets / configmap locally per database resource?

Hi @FxKu, yes, we use the global pod_environment_configmap option to reference a ConfigMap at the operator level.
For this use case, we need to additionally reference a workload-specific ConfigMap with a generated name that provides the SDK environment variables for mounted cloud credentials or OIDC token paths. Since pod_environment_configmap can only point to one ConfigMap per operator configuration, it does not cover this case without merging unrelated configuration. envFrom lets us add that workload-specific reference directly on the database resource that needs it.

[FxKu]

@annielzy can you rebase? I think then we can merge it.

[FxKu]

I resolved the conflicts. We have to provide a paragraph at the end of this admin doc chapter.