Giters

kubeflow / fairing

Python SDK for building, training, and deploying ML models

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Serving with seldom failing

midhun1998 opened this issue · comments

commented

/kind bug /kind question

  • Edited and used XGBoost example to try fairing in Kubeflow in EKS.
  • ClusterBuilder.build() was successfully building the image and pushing to ECR.
  • Serving deployer was used to deploy an endpoint.
  • The pod was deployed with Seldon running inside.
  • The pod crashed with an error.(Attaching a screenshot)
    IMG_20201210_145935_LL.jpg

What did you expect to happen:

  • Expected Seldon to deploy and run with REST argument.

Anything else you would like to add:
I have a doubt if Seldon 1.5.0 still supports the REST argument. Also when I ran a pod with a similar deployment spec but without REST argument the pod was running fine.

Environment:

  • Fairing version: 1.0.1
  • Kubeflow version: (version number can be found at the bottom left corner of the Kubeflow dashboard): v1beta1
  • Kubernetes version: (use kubectl version): 1.17
commented

@midhun1998: The label(s) kind//kind cannot be applied, because the repository doesn't have them

In response to this:

/kind bug /kind question

  • Used XGBoost example to deploy in kubeflow.
  • Builder was successfully building the image and pushing.
  • Serving deployer was used to deploy an endpoint.
  • The pod was deployed with seldon.
  • The pod crashed with following error.(Attaching a screenshot)
    IMG_20201210_145935_LL.jpg

What did you expect to happen:

  • Expected seldon to deploy and run with REST argument.

Anything else you would like to add:
I have a doubt if seldon 1.5.0 still supports REST argument. Also when i ran a pod with similar deployment spec but without REST argument the pod was running fine.

Environment:

  • Fairing version: 1.0.1
  • Kubeflow version: (version number can be found at the bottom left corner of the Kubeflow dashboard): v1beta1
  • Kubernetes version: (use kubectl version): 1.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

commented

Yeah, we may need to upgrade that.

commented

Hi @jinchihe . Thanks for confirming. If only the REST argument has to be removed from here I can create a PR because I'm just getting started with Kubeflow and seems like a good first issue. If I'm wrong please do guide me.

P.S: I just realized it is not right to remove that argument as it may disrupt backward compatibility. If you feel it's a good first issue do provide some guidance. Thanks. 😄

commented

Yeah, That's great if you can create a PR with your investigation. Thanks!