kyma-project / kyma-project/gpu-driver
Template CRD image defaults from values.yaml
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Description
- Replace hardcoded
default:values fordevicePlugin.image,devicePlugin.repository,devicePlugin.version,installer.image, andinstaller.repositoryincrd.yamlwith Helm template expressions ({{ .Values.* }}) - Add corresponding
devicePluginandinstallersections tovalues.yamlwith the same defaults as before
Reasons
CRD schema defaults were previously hardcoded, requiring a chart source edit to change images at deploy time. Now they can be overridden via --set or a custom values.yaml like any other chart value.
Test plan
-
helm template . --debugrenders CRD with correct defaults from values.yaml - Override via
--set devicePlugin.version=X.Y.Zproduces correct default in rendered CRD -
helm installwith default values behaves identically to previous chart version
Attachments
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
Review crd.yaml and values.yaml, then run helm template . --debug to inspect the rendered CRD defaults. Verify that the existing defaults are represented in values.yaml, Helm overrides such as --set devicePlugin.version=X.Y.Z appear in the CRD, and default installation behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100