- 
                Notifications
    
You must be signed in to change notification settings  - Fork 144
 
KFserving ERROR when running 'Kubeflow E2E MNIST Case' #556
Description
Environment:
- Fairing version: 1.0.1:
 - Kubeflow version: I deploy the Kubeflow by kustomize (https://github.com/kubeflow/manifests/tree/v1.3.0-rc.0#cert-manager)
 - Kubernetes version: v1.18.9:
 - OS : Centos7
 
I have such an error when running "Kubeflow E2E MNIST Case"
‘’‘
Traceback (most recent call last):
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kfserving/api/kf_serving_client.py", line 107, in create
inferenceservice)
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kubernetes/client/apis/custom_objects_api.py", line 178, in create_namespaced_custom_object
(data) = self.create_namespaced_custom_object_with_http_info(group, version, namespace, plural, body, **kwargs)
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kubernetes/client/apis/custom_objects_api.py", line 277, in create_namespaced_custom_object_with_http_info
collection_formats=collection_formats)
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kubernetes/client/api_client.py", line 334, in call_api
_return_http_data_only, collection_formats, _preload_content, _request_timeout)
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kubernetes/client/api_client.py", line 168, in __call_api
_request_timeout=_request_timeout)
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kubernetes/client/api_client.py", line 377, in request
body=body)
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kubernetes/client/rest.py", line 266, in POST
body=body)
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kubernetes/client/rest.py", line 222, in request
raise ApiException(http_resp=r)
kubernetes.client.rest.ApiException: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'Date': 'Wed, 05 May 2021 05:35:08 GMT', 'Content-Length': '391'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"admission webhook "inferenceservice.kfserving-webhook-server.validator" denied the request: Canary rollout is no longer supported on v1alpha2, please convert to v1beta1 to use the feature.","reason":"Canary rollout is no longer supported on v1alpha2, please convert to v1beta1 to use the feature.","code":403}
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "serving.py", line 11, in 
isvc.deploy(isvc.generate_isvc())
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kubeflow/fairing/deployers/kfserving/kfserving.py", line 120, in deploy
self.namespace, self.generate_isvc())
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kubeflow/fairing/kubernetes/manager.py", line 159, in create_isvc
created_isvc = KFServing.create(isvc, namespace=namespace)
File "/root/miniconda3/envs/kfserving/lib/python3.6/site-packages/kfserving/api/kf_serving_client.py", line 111, in create
%s\n" % e)
RuntimeError: Exception when calling CustomObjectsApi->create_namespaced_custom_object:                 (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'Date': 'Wed, 05 May 2021 05:35:08 GMT', 'Content-Length': '391'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"admission webhook "inferenceservice.kfserving-webhook-server.validator" denied the request: Canary rollout is no longer supported on v1alpha2, please convert to v1beta1 to use the feature.","reason":"Canary rollout is no longer supported on v1alpha2, please convert to v1beta1 to use the feature.","code":403}
’‘’
I got this erroe when I was using KFserving to deploy the inferenceservice. The specific code is:
kfserving_client = KFServingClient()
kfserving_client.get(namespace=my_namespace))
I want to know why there is such a problem, whether it is related to the version of k8s