-
Notifications
You must be signed in to change notification settings - Fork 769
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
fix: unreliable webhook behaviour on gatekeeper pod startup and shutdown #3780
base: master
Are you sure you want to change the base?
fix: unreliable webhook behaviour on gatekeeper pod startup and shutdown #3780
Conversation
46de743
to
937a91e
Compare
937a91e
to
fcd6e13
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
Signed-off-by: Benjamin Ritter <benjamin.ritter@stackit.cloud>
Signed-off-by: Benjamin Ritter <benjamin.ritter@stackit.cloud>
Co-authored-by: Jaydip Gabani <gabanijaydip@gmail.com> Signed-off-by: Benjamin Ritter <7373184+l0wl3vel@users.noreply.github.com>
fe4bc04
to
262f5c4
Compare
@JaydipGabani Integrated your suggestion. Could you please rerun the workflows? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3780 +/- ##
==========================================
- Coverage 54.49% 47.72% -6.77%
==========================================
Files 134 236 +102
Lines 12329 19929 +7600
==========================================
+ Hits 6719 9512 +2793
- Misses 5116 9525 +4409
- Partials 494 892 +398
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
What this PR does / why we need it:
This PR fixes webhook requests getting routed to starting and stopping gatekeeper pods, that are not ready to serve requests. The implications of this behaviour are explained in #3776
Which issue(s) this PR fixes:
Fixes #3776
Special notes for your reviewer:
The grace period for handling termination will not work when using Tilt to test. It will terminate instantly, like it did before.
We tracked this down to the rerun-process-handler Tilt uses to wrap the application to test.
The start.sh script traps SIGTERM and INTERRUPTS, the two signals we handle, and replaces them with SIGKILL, which we do not intercept.
Running
make run
yields the intended behaviour.Co-authored by Nils Federle (@nilsfed) and Paweł Kukliński (@pawelkuk)