[FEATURE]: CR/Values Private Repository

[OA72280]

For those customers who cannot allow the CSI to pull various container images from external registries, it would be beneficial to adopt a configmap process that does the following:

DEFAULT

apiVersion: v1 kind: ConfigMap metadata: name: image-registry-config namespace: your-namespace data: registryAddress: "docker.io/dellemc"

Customer Registry

apiVersion: v1 kind: ConfigMap metadata: name: image-registry-config namespace: your-namespace data: registryAddress: "my-container-repo/"

This approach would then ensure that any values or CR file is able to utilize the amended registry such that a values or CR file does not need to be manually updated as this could lead to accidental omissions and typo's etc.,

This would also allow future updates to be done where those values and CR files needn't be edited as well.

[csmbot]

@OA72280: Thank you for submitting this issue!

The issue is currently awaiting triage. Please make sure you have given us as much context as possible.

If the maintainers determine this is a relevant issue, they will remove the needs-triage label and respond appropriately.

---

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected].

[shanmydell]

With the Operator there is a recommendation here: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/#other-common-suggestions ; with plain Kubernetes resources we have the image attribute, with helm deployment it is already properly tackled per standard practices: https://github.com/dell/helm-charts/blob/main/charts/csi-isilon/values.yaml#L7