-
Notifications
You must be signed in to change notification settings - Fork 3k
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
envoy: fix lb backend endpoint calculation #27923
envoy: fix lb backend endpoint calculation #27923
Conversation
/test |
This pull request has been automatically marked as stale because it |
Looks good, sorry for the delay, was there an issue for this bug? |
eee6047
to
0ba766b
Compare
This commit extracts the logic that creates Envoy endpoints (ClusterLoadAssignments) for LoadBalancing Backends into its function. In addition some unit tests were added. Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
Currently, mapping loadbalancing backends to Envoy endpoints contains a bug that the LbEndpoints are kept/appended over the whole backendMap. Therefore, later endpoints will contain the LBEndpoints of all previous backends. This commit fixes this by putting the variable `lbEndpoints` into the right scope (per port). Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
0ba766b
to
044da91
Compare
rebased to |
no problem. no there isn't a reported issue. |
/test |
@mhofstetter This probably needs backports right? (looks like the same issue might exist back to at least v1.13). |
Currently, mapping loadbalancing backends to Envoy endpoints contains a bug that the LbEndpoints are kept/appended over the
whole backendMap. Therefore, later endpoints will contain the LBEndpoints of all previous backends.
This commit fixes this by putting the variable
lbEndpoints
into the right scope (per port).