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.

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

Eliminate/prevent dependencies on extensions from core #9953

Closed
mergeconflict opened this issue Feb 6, 2020 · 7 comments · Fixed by #20614
Closed

Eliminate/prevent dependencies on extensions from core #9953

mergeconflict opened this issue Feb 6, 2020 · 7 comments · Fixed by #20614
Assignees
Labels
Milestone

Comments

@mergeconflict
Copy link
Member

There are some cases where core Envoy code (or tests) depends on extensions. One example:

//source/extensions/access_loggers/grpc:http_config
//source/extensions/access_loggers/grpc:tcp_config

are used by:

//test/integration/http2_upstream_integration_test
//test/common/access_log/access_log_impl_test

This poses an issue for users like Google, who import only specific whitelisted extensions. We have to disable tests that depend on non-whitelisted extensions. I think we'd like to add some logic to check_format or similar, to catch these dependencies before they're introduced.

Not sure if this is related to #7903, likely seems related to #2910.

@mattklein123
Copy link
Member

+1 yes please. If you are going to fix this can you also potentially fix #6736? It's related in the sense that by default we build and link all extensions into some of the server integration tests. Optimally the core integration tests should depend on only a build with a very limited set of extensions.

@mattklein123 mattklein123 added this to the 1.15.0 milestone May 5, 2020
@mattklein123
Copy link
Member

I think @yanavlasov is working on this. Also discussing fixing #6736 as well.

@mattklein123 mattklein123 modified the milestones: 1.15.0, 1.16.0 Jun 24, 2020
@antoniovicente
Copy link
Contributor

Related: #12315 #12314

@alyssawilk alyssawilk self-assigned this Jul 28, 2020
@alyssawilk alyssawilk removed their assignment Jul 28, 2020
lizan pushed a commit that referenced this issue Aug 1, 2020
Risk Level: medium (of build breakage)
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Part of #9953

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
chaoqin-li1123 pushed a commit to chaoqin-li1123/envoy that referenced this issue Aug 7, 2020
…proxy#12337)

Risk Level: medium (of build breakage)
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Part of envoyproxy#9953

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
chaoqin-li1123 pushed a commit to chaoqin-li1123/envoy that referenced this issue Aug 7, 2020
…proxy#12337)

Risk Level: medium (of build breakage)
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Part of envoyproxy#9953

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: chaoqinli <chaoqinli@google.com>
@mattklein123 mattklein123 modified the milestones: 1.16.0, 1.17.0 Oct 4, 2020
@mattklein123 mattklein123 modified the milestones: 1.17.0, 1.18.0 Jan 7, 2021
@antoniovicente
Copy link
Contributor

Tests for core extension (TLS) depending on non-core extension with new cert verifier functionality -> broken build if you only want the transport_sockets TLS extension.

#14884

alyssawilk added a commit that referenced this issue Dec 14, 2021
part of #9953

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
@alyssawilk alyssawilk modified the milestones: 1.21.0, 1.22.0 Jan 10, 2022
alyssawilk added a commit that referenced this issue Jan 13, 2022
Risk Level: low
Testing: n/a
Docs Changes: n/a
Release Notes: inline
part of #9953

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
htuch pushed a commit that referenced this issue Feb 9, 2022
Part of #9953

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
joshperry pushed a commit to joshperry/envoy that referenced this issue Feb 13, 2022
part of envoyproxy#9953

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Josh Perry <josh.perry@mx.com>
joshperry pushed a commit to joshperry/envoy that referenced this issue Feb 13, 2022
Risk Level: low
Testing: n/a
Docs Changes: n/a
Release Notes: inline
part of envoyproxy#9953

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Josh Perry <josh.perry@mx.com>
joshperry pushed a commit to joshperry/envoy that referenced this issue Feb 13, 2022
Part of envoyproxy#9953

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Josh Perry <josh.perry@mx.com>
@mattklein123
Copy link
Member

I think @alyssawilk has been picking away at this. @alyssawilk are we done with this or is there more to do?

@alyssawilk
Copy link
Contributor

Down from ~30 to ~6 but not compelte

source/extensions/filters/network/common/BUILD: # Used by core. TODO(#9953) clean up.
source/extensions/filters/http/buffer/BUILD: # Legacy test use. TODO(#9953) clean up.
source/extensions/filters/http/ip_tagging/BUILD: # TODO(#9953) clean up.
source/extensions/filters/listener/tls_inspector/BUILD: # TODO(#9953) clean up.
source/extensions/filters/listener/tls_inspector/BUILD: # TODO(#9953) clean up.
source/extensions/access_loggers/file/BUILD: # TODO(#9953) determine if this is core or should be cleaned up.

@alyssawilk
Copy link
Contributor

DONE.

ravenblackx pushed a commit to ravenblackx/envoy that referenced this issue Jun 8, 2022
ravenblackx pushed a commit to ravenblackx/envoy that referenced this issue Jun 8, 2022
Risk Level: n/a (visibility only)
part of envoyproxy#9953
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
ravenblackx pushed a commit to ravenblackx/envoy that referenced this issue Jun 8, 2022
ravenblackx pushed a commit to ravenblackx/envoy that referenced this issue Jun 8, 2022
Fixes envoyproxy#9953

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants