Please do not suggest insecure k8s practices.

https://github.com/hasura/graphql-engine/blob/master/docs/graphql/core/deployment/deployment-guides/kubernetes.rst#step-2-set-the-postgres-database-url

I don't know much about k8s, but I do know for darn certain that 1) your postgres should *always* be secured and 2) you should NEVER store your pg login in a deployment.yml file. Luckily k8s has a secret store that allows you to store sensitive data like postgres passwords.

Please upgrade the docs as you are promoting insecurity by default.

Cheers!

Start with docs/graphql/core/deployment/deployment-guides/kubernetes.rst at “Step 2: Set the Postgres Database URL.” Review how the deployment.yml example handles the Postgres login, then update the guide to use Kubernetes Secrets for sensitive credentials. Done means the default instructions no longer place the login directly in deployment.yml and clearly explain the secure approach.

Written by the indexing model from the issue text.