-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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(core): dyn upstream keepalive #9856
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chronolaw
changed the title
fix(patches): dyn upstream keepalive (WIP)
fix(core): dyn upstream keepalive (WIP)
Dec 2, 2022
chronolaw
force-pushed
the
fix/dyn_upstream_keepalive
branch
from
December 4, 2022 06:11
b180539
to
113e627
Compare
github-actions
bot
added
the
chore
Not part of the core functionality of kong, but still needed
label
Dec 4, 2022
chronolaw
changed the title
fix(core): dyn upstream keepalive (WIP)
fix(core): dyn upstream keepalive
Dec 5, 2022
chronolaw
added
core/balancer
and removed
chore
Not part of the core functionality of kong, but still needed
labels
Dec 5, 2022
github-actions
bot
added
chore
Not part of the core functionality of kong, but still needed
and removed
core/balancer
labels
Dec 5, 2022
chronolaw
commented
Dec 6, 2022
ADD-SP
force-pushed
the
fix/dyn_upstream_keepalive
branch
from
December 6, 2022 08:42
1e36e7e
to
cd895d8
Compare
github-actions
bot
removed
the
chore
Not part of the core functionality of kong, but still needed
label
Dec 28, 2022
@chronolaw I squashed and rebased the commits, to fix failing ci. |
chronolaw
force-pushed
the
fix/dyn_upstream_keepalive
branch
from
January 11, 2023 06:10
fc91a69
to
92c2caa
Compare
chronolaw
force-pushed
the
fix/dyn_upstream_keepalive
branch
from
January 30, 2023 03:14
92c2caa
to
deb8ebc
Compare
chronolaw
force-pushed
the
fix/dyn_upstream_keepalive
branch
4 times, most recently
from
February 6, 2023 03:48
f13880e
to
93476ad
Compare
chronolaw
force-pushed
the
fix/dyn_upstream_keepalive
branch
from
February 8, 2023 05:59
93476ad
to
29d4f18
Compare
when do this fix to be released? We are wait it to apply for out environment😁 |
I have the same feeling as you. Perhaps it will be released in Kong 3.3. |
chronolaw
force-pushed
the
fix/dyn_upstream_keepalive
branch
2 times, most recently
from
February 22, 2023 06:59
50b51c2
to
f5596bf
Compare
chronolaw
force-pushed
the
fix/dyn_upstream_keepalive
branch
from
March 7, 2023 03:21
db22e49
to
ad0fb95
Compare
oowl
pushed a commit
that referenced
this pull request
Aug 15, 2024
…()` (#9856) This function will be used in EE. KAG-4698 (cherry picked from commit #13431) Co-authored-by: Niklaus Schen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
See issue #9582,
Related PR: Kong/kong-build-tools#619
Ticket: KAG-294
Checklist
Full changelog
build/openresty/patches
Issue reference
Fix #[9582]