Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Test TCPIngress behavior when upstream disappears #2068

Closed
1 of 2 tasks
rainest opened this issue Dec 9, 2021 · 2 comments
Closed
1 of 2 tasks

Test TCPIngress behavior when upstream disappears #2068

rainest opened this issue Dec 9, 2021 · 2 comments
Labels
area/tests priority/medium wontfix This will not be worked on

Comments

@rainest
Copy link
Contributor

rainest commented Dec 9, 2021

Is there an existing issue for this?

  • I have searched the existing issues

Problem Statement

Broken out of #1179

Proposed Solution

No response

Additional information

No response

Acceptance Criteria

Tests confirm that:

  • Long running persistent connections (where the backend server doesn't support reconnect mechanisms) disconnect and fail properly when pods change
@rainest
Copy link
Contributor Author

rainest commented Dec 9, 2021

Per #1179 (comment), this is all NGINX-level behavior. AFAIK Kong has no control over the connection once established, and cannot set any NGINX-level configuration that would influence this behavior.

@rainest rainest mentioned this issue Dec 9, 2021
Closed
14 tasks
@mflendrich mflendrich added the wontfix This will not be worked on label Apr 5, 2022
@mflendrich
Copy link
Contributor

Closing as won't fix per @rainest's comment above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/tests priority/medium wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rainest @mflendrich @shaneutt