Matteo Mortari
Matteo Mortari
/lifecycle frozen We will need this
this work would also partially cover for the requirements from: - https://github.com/kubeflow/model-registry/pull/66#issuecomment-2232347605
this is being worked with: https://github.com/kubeflow/model-registry/pull/154
/reopen I believe all boxes are meant be ticked, to review.
> I believe all boxes are meant be ticked, to review. thank you @lampajr @Al-Pragliola for confirming all boxes can be ticket.
marking as Complete.
With the MR python client rebase on REST (https://github.com/kubeflow/model-registry/pull/152) this appears to no longer be needed, so we're going to close this. For more information: https://github.com/kubeflow/model-registry/issues/181 If you believe this...
We need this (maybe reframed, rescoped) as part of roadmap. /lifecycle frozen
I would rather have this pov: this networkpolicy proposal aligns with other examples as suggested by action item out of previous meeting (notes). In short we need 2 "endpoints": REST...
I've added https://github.com/kubeflow/manifests/pull/2724/commits/31345c974f814d0af9c62b51cb46d73c750b50a8 but I need to test it on a vanilla KF cluster, hence keeping this as draft for now. Would this align better to expectations, please?