zalando / zalando/postgres-operator
Allow specifying nodeSelector for cloned database
Nobody has claimed this yet.
- 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?
- Currently using registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
- Kubernetes
- Running in Pord
- Bug report
When trying to create a clone database from s3 specifying nodeSelectors I get the following error:
Error from server (BadRequest): error when creating "db-clone-test.yaml": postgresql in version "v1" cannot be handled as a postgresql: strict decoding error: unknown field "spec.nodeSelect
My yaml is pretty basic and looks like
apiVersion: "acid.zalan.do/v1"
kind: postgresql
metadata:
name: db-clone
namespace: test
spec:
clone:
uid: "0a4ascaf-159e-4cac-8ee3-5292fe46f5"
cluster: "source-db"
timestamp: "2024-03-12T00:00:33-08:00"
...
nodeSelector:
node-role.kubernetes.io/cluster-apps: ""
tolerations:
- key: node-role.kubernetes.io/cluster-apps
operator: Equal
effect: NoSchedule
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named in the issue. Start by tracing validation of the PostgreSQL resource's spec.nodeSelector and the clone path, using the provided YAML to reproduce the strict-decoding error; done means a cloned database accepts nodeSelector and tolerations and schedules accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100