-
Notifications
You must be signed in to change notification settings - Fork 4k
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
VPA E2E tests are failing #4557
Comments
#4537 merged on 2021-12-20 17:02 CET and affects admission controller, that's why I suspect it causes the problem. |
This reverts commit dfce769. Reason for reverting the change is that I suspect it broke our E2E tests: see issue kubernetes#4557
When I run e2e tests in my cluster from current master in logs of API server I see logs like:
|
What do you have configured for |
Is there a way I can run the E2E tests suite locally, on my laptop? |
I don't know. I create a cluster and use |
|
Admission controller responses are rejected with ``` failed calling webhook "vpa.k8s.io": expected webhook response of admission.k8s.io/v1, Kind=AdmissionReview, got /, Kind= ``` Fix this by setting fields API server expects us to set. Fixes kubernetes#4557
VPA e2e tests are consistently failing. They were consistently passing (flake once every few days) until recently.
For
full
suite:For
admission-controller
:For
actuation
:It looks like admission-controller is broken. I suspect that the culprit is #4537
The text was updated successfully, but these errors were encountered: