Skip to content

Clearer way to map PVCs to PVs for Static Volumes #1131

Open
@curionim

Description

@curionim
  • Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.5.0
  • **Where do you run it - cloud or metal? Bare Metal K8s
  • Are you running Postgres Operator in production? yes
  • Type of issue? feature request

When running on cluster without dynamic volumes, i.e. PVs are statically created, the operator will try to create a PVC for each replica and bind it to available PVs based on storage class name and size.
We would like to be able to explicitly select which PVs to use, for instance by allowing for static PVCs, or by using selectors.
Is it possible already?

Thanks,
Michele

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