-
Notifications
You must be signed in to change notification settings - Fork 597
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: fix Kong client's status check #6689
Conversation
93aadef
to
d05938a
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6689 +/- ##
=======================================
+ Coverage 77.7% 77.9% +0.1%
=======================================
Files 203 204 +1
Lines 23836 23903 +67
=======================================
+ Hits 18534 18631 +97
+ Misses 4351 4324 -27
+ Partials 951 948 -3 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
d05938a
to
0b289e5
Compare
cf9b8f7
to
1d2421a
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.
Good catch 🎖️
1d2421a
to
cef96bc
Compare
cef96bc
to
1c455d7
Compare
What this PR does / why we need it:
This PR fixes an invalid status check in kong client which causes the client to report that it's ready while in reality it's not. The problem arises from an invalid check in
NewKongClientForWorkspace()
which short circuits when the workspace is empty and does not perform the checks that follow.
The above causes the client manager to think that this client is ready to receive config where it's not.
This behavior can easily be tested with using Gateway Discovery and scaling up the Kong
Deployment
. This also prevents theKongConfigurationApplyFailed
event from being created.Which issue this PR fixes:
Special notes for your reviewer:
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR