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

Cannot view endpoint details on Kubeflow. #528

Open
muratyarali opened this issue Nov 21, 2024 · 0 comments
Open

Cannot view endpoint details on Kubeflow. #528

muratyarali opened this issue Nov 21, 2024 · 0 comments

Comments

@muratyarali
Copy link

muratyarali commented Nov 21, 2024

I deployed ModelMesh-Serving in a Kubeflow K8S cluster (kubeflow version: v1.9.1-RC.2) and created an InferenceService (ISVC) with modelmesh as follows:

kubectl apply -f - <<EOF
apiVersion: serving.kserve.io/v1beta1
kind: InferenceService
metadata:
  name: example-sklearn-isvc
  namespace: modelmesh-serving
  annotations:
    serving.kserve.io/deploymentMode: ModelMesh
spec:
  predictor:
    model:
      modelFormat:
        name: sklearn
      storageUri: "gs://kfserving-examples/models/sklearn/1.0/model"
EOF

Annotation is used to select the model mesh for deploying an ISVC. When I create an ISVC with KServe (without annotation), I can view it on the KServe Endpoints tab in the Kubeflow UI, and clicking on it reveals the details.

However, when I create the ISVC with ModelMesh-Serving, I can see it listed in the KServe Endpoints tab, but clicking on it does not display the details and instead shows an error:

[404] The requested resource could not be found in the API Server https://www.example.com/kserve-endpoints/api/namespaces/modelmesh-serving/revisions/undefined

The Kubeflow-UI is looking for resources at /kserve-endpoints/api/namespaces/modelmesh-serving/revisions/ which don't exist for ModelMesh.

Can this be fixed or extended on the Kubeflow or ModelMesh-Serving side?

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

No branches or pull requests

1 participant