[Question]: Is the omission of env support for the operator Deployment intentional?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 552
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 90
Description
All components in the chart (validator, driver, toolkit, devicePlugin, dcgm, gfd, migManager, etc.) support custom env injection via values.yaml, and these are rendered in clusterpolicy.yaml. However, the operator Deployment in templates/operator.yaml only has three hardcoded env vars (WATCH_NAMESPACE, OPERATOR_NAMESPACE, DRIVER_MANAGER_IMAGE) and does not support additional env injection through values.
Is this an intentional design decision to restrict the operator container's environment, or would a PR adding operator.env support be welcome?
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 templates/operator.yaml and values.yaml, then compare the existing environment injection rendered through clusterpolicy.yaml for the other components. Confirm with maintainers whether operator.env is intended; done means the expected behavior and scope are decided, with any approved support covered by the relevant chart checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100