[Feature]: Add In-Cluster Driver Image Registry Support for KMM-Operator
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 105
- Forks
- 57
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 12
Description
Suggestion Description
Hi! I think it will be nice if the gpu-operator can automatically add an in-cluster driver image registry to host the driver images built by KMM-operator when the user does not provide a private driver image registry and .driver.enable is set to true in the deviceconfig crd. This feature can be nice for closed environments with limited access to private registries. It might also be useful for rapid and easy deployment of amd gpu operator without worrying about preparing a dedicated driver registry beforehand. Thank you in advance!
Operating System
No response
GPU
No response
ROCm Component
kmm-operator, operator-controller-manager
Contributor guide
No contributing guide indexed for this repository
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 tracing the KMM-operator and operator-controller-manager integration points for the DeviceConfig CRD, focusing on the .driver.enable setting and private registry handling. Done means an in-cluster driver image registry is automatically available when no private registry is provided, while existing private-registry deployments continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100