Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Kubeflow Model Registry Network Policies #2701

Closed
lampajr opened this issue May 2, 2024 · 3 comments · Fixed by #2724
Closed

Add Kubeflow Model Registry Network Policies #2701

lampajr opened this issue May 2, 2024 · 3 comments · Fixed by #2724
Assignees

Comments

@lampajr
Copy link
Member

lampajr commented May 2, 2024

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 and 9090, the gRPC interface) ?

NOTE: This is a non-blocker for Kubeflow 1.9 release as KFMR won't be deployed by default

@lampajr
Copy link
Member Author

lampajr commented May 2, 2024

fyi @tarilabs @rimolive

@juliusvonkohout
Copy link
Member

"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.

Needs Triage automation moved this from To Do to Closed Jun 3, 2024
@kubeflow-bot kubeflow-bot removed this from Closed in Needs Triage Jun 3, 2024
@tarilabs
Copy link
Member

tarilabs commented Jun 3, 2024

/assign @tarilabs

(data mgt)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants