-
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
Moving the connection info into a single provider #17168
Labels
Comments
The first step is #16574, working on others. |
mattklein123
added
area/connection
help wanted
Needs help!
tech debt
and removed
triage
Issue requires triage
labels
Jun 28, 2021
ggreenway
pushed a commit
that referenced
this issue
Aug 4, 2021
Part of #17168 Signed-off-by: He Jie Xu <hejie.xu@intel.com>
This was referenced Aug 24, 2021
leyao-daily
pushed a commit
to leyao-daily/envoy
that referenced
this issue
Sep 30, 2021
…17334) Part of envoyproxy#17168 Signed-off-by: He Jie Xu <hejie.xu@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Title: Moving the connection info into a single provider
Description:
According to the discussion on the PR #16574 (comment), there are connection Infos are coping around which leads to the bug like #14922. So plan to fix this kind of issue using the way like #14133 way: moving those infos into a single provider.
So separate the fix by following steps:
The text was updated successfully, but these errors were encountered: