Support pod affinity rule configuration for web pods
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
The Pulp Operator allows configuring affinity rules for the api, worker, and content components, but not for the web pod. This makes it impossible to control pod placement for web pods in the same way as the other components, which can be an issue in highly available or production environments.
Describe the solution you'd like
Expose affinity rule configuration for the web pod, consistent with the existing support for api, worker, and content.
Additional context
The difference in supported fields can be seen in the CRD definition:
https://github.com/pulp/pulp-operator/blob/main/config/crd/bases/repo-manager.pulpproject.org_pulps.yaml
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
Start with config/crd/bases/repo-manager.pulpproject.org_pulps.yaml and compare the web pod fields with the existing api, worker, and content affinity configuration. Expose equivalent affinity rule configuration for web pods and verify that the generated CRD reflects the new field.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100