Dhiraj Bokde

For reference, the [openapi-generator](https://github.com/OpenAPITools/openapi-generator) golang generator handles this design by correctly combining the composed properties from Base* types.

I updated the link to the proposal in the description to a google doc we created for Kubeflow community discussions.

This sort of solves the problem for model registry REST API. But I think we can solve it for both REST and gRPC by re-using some bits from our model...

BTW, url rewrite will break any clients that are using full paths declared in the REST API.

@tarilabs I created a PR on your repo branch https://github.com/tarilabs/model-registry/pull/2 Can you test it in your cluster and verify that it resolves both REST and gRPC routing without conflicting with...

Yes to cluster scope single registry for uri prefix check question. As discussed previously, we have additional port and authority checks to avoid collisions with mlmd virtual service. I also...

After discussion with @ederign the proposal is to use the following locations to group ui code under client parent directory: `client/ui/{bff|backend} client/ui/frontend` To lookup model registry k8s resources for UI,...

The midstream model registry operator in ODH uses a slightly different set of [labels](https://github.com/opendatahub-io/model-registry-operator/blob/main/internal/controller/config/templates/service.yaml.tmpl#L6-L14) for model registry services. We need to update upstream manifests to also use the same labels...

@tarilabs is there a label to disable the stale marker?

@rchincha thanks for this proposal. There is certainly a lot of interest around OCI registry for ML model data. One of the ideas being discussed within the model registry team...