-
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
webhook: cache miss fallback to direct client for ScaledObject #6186
webhook: cache miss fallback to direct client for ScaledObject #6186
Conversation
9895f0d
to
0796a20
Compare
Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com>
0796a20
to
6d38faf
Compare
for helm, this is just a matter of extraArgs:
webhooks:
cache-miss-to-direct-client: "true" |
/run-e2e |
/run-e2e internal |
I think that the failure is related with this PR and not with your changes -> #6196 |
/run-e2e internal |
/run-e2e internal |
/run-e2e internal |
/run-e2e azureeventgridtopic |
…ore#6186) Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com> Co-authored-by: Zbynek Roubalik <zroubalik@gmail.com>
…ore#6186) Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com> Co-authored-by: Zbynek Roubalik <zroubalik@gmail.com> Signed-off-by: michael pechner <mike.pechner@akasa.com>
When creating
Deployment
andScaledObject
as part of a single helm chart / manifests file, it's possible to hit a race condition when webhook rejectsScaledObject
because the cached kubernetes client doesn't see theDeployment
yet. This PR adds a fallback option with--cache-miss-to-direct-client
command line parameter, when set to true, if there was a cache miss (GET
returned errorIsNotFound
), validating webhook will attempt the sameGET
but using the direct REST kubernetes client.Checklist
Fixes #5973