-
Notifications
You must be signed in to change notification settings - Fork 879
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
Upgrade Knative serving to 1.10.2 and eventing to 1.10.1 #2486
Upgrade Knative serving to 1.10.2 and eventing to 1.10.1 #2486
Conversation
2df1a82
to
69500fc
Compare
Signed-off-by: Anna Jung (VMware) <[email protected]>
Signed-off-by: Anna Jung (VMware) <[email protected]>
f52e907
to
4b85b83
Compare
I used upterm to see what's happening inside the cluster, and it looks like a few of the pods are not coming up because of insufficient resources, so they're in a pending state until the timeout hits, which results in a failed test. I will take a deeper look into it this week |
d1781bd
to
c75072f
Compare
Due to insufficient resources and the default setting that does not allow scheduling pods on the control plane nodes, at some point in the test, pods cannot run and stay in the pending state and fails to meet the condition check for all pods in "ready" state. It looks like there are two approaches to solving the issue, both have been tested and were successful in running the KServe test
Not sure which one is better approach @kimwnasptd thoughts? |
@annajung I'd also vote for adding another worker node in our config file, just to unblock us for now. |
Signed-off-by: Anna Jung (VMware) <[email protected]>
c75072f
to
e7353aa
Compare
@yuzisun Looks like KServe is using serving 1.10.1 and eventing 1.10.0 according to the quick install script and the github actions, do you have any concerns with 1.10.2 and eventing 1.10.1? we like to get this in before the feature freeze Aug 2nd |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: annajung, kimwnasptd The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Which issue is resolved by this Pull Request:
Part of #2450
Description of your changes:
cc @kimwnasptd