zalando / zalando/postgres-operator
Postgres pods fail to schedule on a mixed linux/windows kubernetes cluster
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?
- 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? Kubernetes or OpenShift? Azure AKS
- Are you running Postgres Operator in production? yes
- Type of issue? Bug report
The operator does not add the
nodeSelector:
kubernetes.io/os: "linux"
bit to the postgres pods. And they fail to schedule if they happen to end up on a Windows node.
We can of course tag those nodes with a NoSchedule for the postgres pods. But since the spilo image will probably never have a Windows version, a better approach would be to include these by default.
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
Locate the operator code that builds PostgreSQL pod specifications and search for existing scheduling-related tests or configuration. Verify how node selectors are represented, then add the Linux selector to the generated pods and confirm that the relevant tests cover scheduling on mixed Linux/Windows clusters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100