Add support for user-defined labels on the Pulp Operator pod
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 does not currently provide a way to configure custom Kubernetes labels on the operator pod itself.
This is a limitation when integrating the operator into clusters that rely on labels for security policies.
Describe the solution you'd like
Provide a supported mechanism to configure custom labels for the Pulp Operator pod, for example via the operator’s Helm chart values.
Describe alternatives you've considered
Manually editing the operator Deployment to add labels, which is overwritten during upgrades or reinstallation.
Using cluster-wide mutating admission webhooks to inject labels, which adds unnecessary complexity and is not specific to the Pulp Operator.
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 by locating the operator's Helm chart values and the Deployment configuration for the operator pod. Trace how configuration reaches the pod metadata, then verify that custom labels remain after upgrades or reinstallations and that the relevant deployment behavior is covered by existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100