Matteo Mortari

this is awesome to hear, thank you @alexcreasy ; I believe I tried only similar combination before podman wired Rosetta, so I'm happy to hear nowadays it gets a lot...

> I want to augment the comment in https://github.com/kubeflow/model-registry/pull/267#pullrequestreview-2244881693 > with the information that the default vanilla installation uses a custom image of mysql from google container registry: > >...

Hi, this is a note of record that regardless we didn't receive any feedback since on enquiry - https://github.com/kubeflow/pipelines/discussions/11224 despite also following up with Liaisons and community in KF Release...

ps.: after #267, we can also consider #703 but I would prefer to keep fifo

we still intend to merge [#703](https://github.com/kubeflow/model-registry/pull/703) in a subsequent MR release(S)

Thank you for this comment @fbricon ! Per the original proposal document for Model Registry, this is accounted, especially for audit purposes. As mentioned in the same document, this intent...

thanks for looping this @rareddy , The requirements are more naturally and clearly emerging recently, here is what I captured so far: - the ability to discover presently running models,...

> Or would the BFF be required to 'talk' with another Kubeflow project (Kserve, perhaps) to provide all data needed for them? I just want to clarify I did not...

> @tarilabs I thought MR created InferenceService entities and with the above use of reconciling we are collating the deployment info which could then directly be exposed through MR REST...

@fbricon this discussion is indeed to _avoiding having to ask users to kubectl get isvc_. This discussion, as the comment are showing, is about implementation choices for how to do...