You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in the last Manifests WG (2nd May, 2024) we need to setup Network Policies for the new Kubeflow Model Registry, this seems required to make the pod accessible from namespaces other than the kubeflow one.
"Do we need to apply network policy for both ports (8080, the REST interface and 9090, the gRPC interface) ?" everything that sould be reachable outside of the Kubeflow namespace must be exposed.
As discussed in the last Manifests WG (2nd May, 2024) we need to setup Network Policies for the new Kubeflow Model Registry, this seems required to make the pod accessible from namespaces other than the
kubeflow
one.The new network policy should be added here: https://github.com/kubeflow/manifests/blob/master/common/networkpolicies/base/
A good starting point, as suggested in the meeting is: https://github.com/kubeflow/manifests/blob/master/common/networkpolicies/base/ml-pipeline.yaml
Open question:
Do we need to apply network policy for both ports (
8080
, the REST interface and9090
, the gRPC interface) ?The text was updated successfully, but these errors were encountered: