[Feature]: Add In-Cluster Driver Image Registry Support for KMM-Operator

[CcccYxx]

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

[yansun1996]

Hi @CcccYxx thanks for trying AMD GPU Operator. Managing an image registry within the cluster requires much more considerations and extra configurations. We have to consider the storage solutions on users cluster and the secure configurations, RBAC configs for pulling/pushing/deleting images. As of now you could consider using the existing Kubernetes in-cluster image registry solutions like:

1. Self-host your image registry by using Harbor: https://artifacthub.io/packages/helm/harbor/harbor or https://artifacthub.io/packages/helm/twuni/docker-registry
2. Use other K8s distributions who provide in-cluster image registry like microk8s or OpenShift.

[CcccYxx]

Hi @yansun1996, Thank you for the suggestions! It makes a lot of sense regarding the complications. I can definitely try those things out first!