loxilb ingress unresponsive after long run #879
Labels
bug
Something isn't working
Comments
TrekkieCoder
added a commit
to loxilb-io/loxilb-ebpf
that referenced
this issue
Nov 16, 2024
TrekkieCoder
added a commit
to loxilb-io/loxilb-ebpf
that referenced
this issue
Nov 16, 2024
loxilb-io/loxilb#879 Rework to avoid race-conditions
TrekkieCoder
added a commit
to TrekkieCoder/loxilb
that referenced
this issue
Nov 16, 2024
UltraInstinct14
added a commit
that referenced
this issue
Nov 16, 2024
gh-879 Fixes for race-conditions in ingress
TrekkieCoder
added a commit
to loxilb-io/loxilb-ebpf
that referenced
this issue
Nov 17, 2024
TrekkieCoder
added a commit
to loxilb-io/loxilb-ebpf
that referenced
this issue
Nov 17, 2024
loxilb-io/loxilb#879 better handling of fd entries on proxy connectio…
TrekkieCoder
added a commit
to TrekkieCoder/loxilb
that referenced
this issue
Nov 17, 2024
UltraInstinct14
added a commit
that referenced
this issue
Nov 17, 2024
gh-879 Fixes for issues with ingress in the long-run
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After deploying loxilb deployment, it is seen that sometimes few of the pods in the deployment become unresponsive.
To Reproduce
After following the guide, and running curls on loop for long-runs, it is seen that some deployment become unresponsive. Although loxilb-ingress is deployed with liveness check, these pods are not restarted.
Expected behavior
These pods should work fine without any issues. If there are issues as well, they should be handled by liveness checks.
Screenshots
N/A
Environment (please complete the following information):
Additional context
LoxiLB L4 running as external mode but it is probably not related.
The text was updated successfully, but these errors were encountered: