-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
applying tensorflow sample gives webhook failure #235
Comments
I've seen this happen sometimes too.. maybe try killing the controller? We may want to consider separating the webhook into a separate container to scale it for redundancy? |
I agree that we should separate the webhook as its own deployment. |
This typically happens when the controller hasn't stood up yet. Agreed the
separating to its own deployment is the way to go.
…On Tue, Jul 9, 2019 at 8:46 AM Dan Sun ***@***.***> wrote:
I agree that we should separate the webhook as its own deployment.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#235>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AATXLCFH4Z6SIQJJQUZID73P6SXF5ANCNFSM4H7FZDRQ>
.
--
</Ellis>
|
Drilling into the kfserving-controller-manager, I find it has this error in the logs:
It goes into CrashLoopBackOff and then every resource deployment in the cluster fails with that webhook issue (even ones not related to KFServing). |
I believe this would be fixed by #231 |
Also I couldn't fix my cluster by running I had to run |
I think this is due to the configmap error. Unless there's something else we can do, I'm going to |
@ellis-bigelow: Closing this issue. In response to this:
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. |
Try this, it worked for me: |
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
Motivation After many attempts to run the FVT tests it became clear that an undersized Kubernetes cluster (insufficient resources) prevented the FVTs to succeed. Modifications Update the FVT README with a Prerequisite section that outlines the required CLIs and the minimum cluster size. Result The FVT tests completed successfully. Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
[Cherry-Pick] Python vulnerability fixes (kserve#3441)
If I try applying the default model directly with
kubectl apply -f https://raw.githubusercontent.com/kubeflow/kfserving/master/docs/samples/tensorflow/tensorflow.yaml
then I get:Note that if I take the other TF model from the canary example (gs://kfserving-samples/models/tensorflow/flowers-2) and apply just that one then it does let me apply the resource.
This is on v0.1.0. Related #233
The text was updated successfully, but these errors were encountered: