zalando / zalando/postgres-operator

SIngle Node, multiple ZFS Pools, allow different Storage Classes for replicas and master (ie split between multiple ZFS Pools)

Open
#2,250 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

idea question
Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

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.9.2
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? [Bare Metal K8s]
  • Are you running Postgres Operator in production? Yes
  • Type of issue? [Question]

We run Single Node and Multi Node CLusters and recently moved storage to ZFS. On our Single Node Clusters, we have 2 mirrored zfs pools, each are mapped to a different openebs provider Storage Class.

We would like to be able to put the master on one storage class, and replicas on another, to keep the data physically separated, and let us use zfs to snapshot the replica only

Is this possible? So far I can not see a way to achieve this, but likely I'm missing something obvious

Many thanks in advance

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository files, tests, or entry points are mentioned. Start by locating the operator configuration for storage classes and master/replica placement, then determine whether separate classes can be assigned on a single node. Done means documenting or implementing a supported way to place the master and replicas on different ZFS-backed storage classes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, postgresql
Domain
databases, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.