Skip to content

How to add some additional env in pg pod? #1807

Description

@cdmikechen

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.7.1
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? OpenShift
  • Are you running Postgres Operator in production? yes
  • Type of issue? question

As I know, I had added a common pod envs by:

pod_environment_configmap: "postgresql-pod-config"

In this configmap, I add some backup envs about wal-g and it works.
But in some cases, I start a pg database for test or dev, I don't want to backup this database log and data. I want to reset these common envs. Or another case, I want to backup a database to another bucket or s3 url.

I didn't find a solution to this problem in the document. So I want to ask whether the operator does not support this case at present? Should we add this feature?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions