-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Activator: Retry on Get Revision error #1573
Comments
We should consider replacing the activator's direct client usage with something informer based. This is only peripherally related to this issue, but is probably how the only real action I'd take on our side to fix this. The activator and activation in general is at the mercy of the availability of the K8s control plane (I've been meaning to write up an issue on this for a while). |
cc @dgerd |
/assign @dgerd I am going to take a stab at replacing the client usage with an informer. |
/unassign I have not made progress on this. Going to unassign for now. |
Thanks for picking this up. Let me know when you need another look at #2653. |
@vvraskin I'm going to put this into 0.4 then /milestone Serving 0.4 |
Moving the work left to 0.5 so that we can bake alongside a new e2e test. |
Hi @vvraskin, do you have any update for this one? Thanks. |
Unfortunately I don't have cycles for this one in the next weeks. |
Gonna pick this up /assign |
/area API
/area autoscale
/kind bug
Expected Behavior
Get revision calls have transient errors. #1558. Activator should deal with that.
Actual Behavior
Activator uses Get revision api as one time shot, sometimes it fails with this error in the log:
Unable to get revision: Get https://10.35.240.1:443/apis/serving.knative.dev/v1alpha1/namespaces/default/revisions/configuration-example-00001: unexpected EOF
In this case, a potential reason is master is down.
Steps to Reproduce the Problem
This usually doesn't happen.
The text was updated successfully, but these errors were encountered: