We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please, answer some short questions which should help us to understand your problem / question better?
authentication.superuser.password field in the postgres.yml is stored in plain text even when we pass Kubernetes Secrets with base64 encoded password.
postgres@rdbms-pg-cluster-dev-1:$ grep -i password postgres.yml password: '' password: RtttSedreSErSSErREreREEsSSSSSSSSsErERer password: Devloper123_ postgres@rdbms-pg-cluster-dev-1:$
Is there any way in Zalando's Postgres Operator to have authentication.superuser.password field in encrypted form?
if encrytion is not possible within Zalando's Postgres Operator then, is there any other way to make postgres.yml more secure?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Please, answer some short questions which should help us to understand your problem / question better?
authentication.superuser.password field in the postgres.yml is stored in plain text even when we pass Kubernetes Secrets with base64 encoded password.
postgres@rdbms-pg-cluster-dev-1:
$ grep -i password postgres.yml$password: ''
password: RtttSedreSErSSErREreREEsSSSSSSSSsErERer
password: Devloper123_
postgres@rdbms-pg-cluster-dev-1:
Is there any way in Zalando's Postgres Operator to have authentication.superuser.password field in encrypted form?
if encrytion is not possible within Zalando's Postgres Operator then, is there any other way to make postgres.yml more secure?
The text was updated successfully, but these errors were encountered: