You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are seeing authentication.superuser.password field in the postgres.yml is stored in plain text even after having Kubernetes Secrets with base64 encoded password.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
we are seeing authentication.superuser.password field in the postgres.yml is stored in plain text even after having Kubernetes Secrets with base64 encoded password.
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?
Beta Was this translation helpful? Give feedback.
All reactions