Inferenceservice status is 'Unknown' with 'IngressNotConfigured'
See original GitHub issue/kind bug
What steps did you take and what happened: My kubeflow and kfserving are installed in k8s, I tried the solution of the issue https://github.com/kubeflow/kfserving/issues/668, but my Inferenceservice is still ‘Unknown’ with ‘IngressNotConfigured’, is there anything missed?
What did you expect to happen: I expect the inferenceservice status is ‘Ready’.
Anything else you would like to add: the inferenceservice revision and configuration are ready, but the route and the service is not ready. Here is
Here is the
And here is the Does is error is complain the virtualservice owner Ingress is missed? actully, there is not the specified Ingress in the same namespace or knative-serving or istio namespace, if the answer is YES, which component should create the ingress?
Environment:
- Istio Version:
- Knative Version: v0.11.1
- KFServing Version: 0.2.2
- Kubeflow version: 1.0.2
- Kfdef:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm]
- Minikube version:
- Kubernetes version: (use
kubectl version
): - OS (e.g. from
/etc/os-release
):
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (8 by maintainers)
Top GitHub Comments
@yuzisun the inference service is a very simple sample here: https://github.com/kubeflow/kfserving/tree/master/docs/samples/custom/hello-world. I had deployed the inference service in my test namespace, everything seems to be the same. the above snapshots are updated.
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! Links: app homepage, dashboard and code for this bot.