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

Moving the connection info into a single provider #17168

Closed
soulxu opened this issue Jun 28, 2021 · 1 comment
Closed

Moving the connection info into a single provider #17168

soulxu opened this issue Jun 28, 2021 · 1 comment
Labels
area/connection help wanted Needs help! tech debt

Comments

@soulxu
Copy link
Member

soulxu commented Jun 28, 2021 •
edited
Loading

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:
@soulxu soulxu added the triage Issue requires triage label Jun 28, 2021
@soulxu soulxu mentioned this issue Jun 28, 2021
Merged
@soulxu
Copy link
Member Author

soulxu commented Jun 28, 2021

The first step is #16574, working on others.

@mattklein123 mattklein123 added area/connection help wanted Needs help! tech debt and removed triage Issue requires triage labels Jun 28, 2021
@soulxu soulxu mentioned this issue Jul 4, 2021
Merged
@soulxu soulxu mentioned this issue Jul 14, 2021
Merged
ggreenway pushed a commit that referenced this issue Aug 4, 2021
@soulxu
tls: move ssl connection info into SocketAddressProvider (#17334)
371099f 
Part of #17168

Signed-off-by: He Jie Xu <hejie.xu@intel.com>
@soulxu soulxu mentioned this issue Aug 15, 2021
Merged
This was referenced Aug 24, 2021
Merged
Merged
leyao-daily pushed a commit to leyao-daily/envoy that referenced this issue Sep 30, 2021
@soulxu
tls: move ssl connection info into SocketAddressProvider (envoyproxy#…
18e7ce1 
…17334)

Part of envoyproxy#17168

Signed-off-by: He Jie Xu <hejie.xu@intel.com>
@soulxu soulxu closed this as completed Nov 2, 2021
@alyssawilk alyssawilk mentioned this issue Nov 4, 2021
Merged
@soulxu soulxu mentioned this issue Apr 5, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/connection help wanted Needs help! tech debt
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@soulxu @mattklein123