[tracker] next steps ModelRegistry Custom Storage Initializer

[tarilabs]

• Add image build directive in the model registry root Makefile (re-using csi Makefile)
• update KServe website, following this: Add ModelRegistry custom storage intializer example kserve/website#346
  to show integration of CSI image here in KF/model-registry instead of the current placeholder of the exampleimage: abc/model-registry-storage-initializer:latest (should read eventually something like image: kubeflow/model-registry-storage-initializer:latest)
  • docs: align ClusterStorageContainer example to latest Kubeflow kserve/website#414
• Set container image registry
• Add some testing focusing on the MR interaction using testcontainers (mocking the download itself)
• add a simple, short "tutorial" on kubeflow.org website ( follow-up with @Al-Pragliola )

Stretch goals:

• Use kiota (or other openapi code-generators) to autogenerate the client, this will make the CSI less dependent on the internal model registry implementation (this will also make the CSI just tied to the openapi spec rather than MR version)
  • Refactor CSI as different command of the model registry module #338

See previous work on this topic:

• Add first draft of model registry kserve custom storage initializer #25 (comment)
• Provide ModelRegistry Custom Storage Initializer #24

If you-reading-this-issue start to work on any of these points, kindly notify by creating a relevant issue, assign it to yourself and reach out to confirm scope with the maintainers :)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tarilabs]

this is being worked with: #154

[lampajr]

Stretch goal being tracked by #338

@tarilabs I think that all non-stretch goals (except for "update KServe website") can be considered as done/completed so I think you can tick the corresponding boxes in this PR's description