orderly cm/cds/rds initialization #482
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We have a fairly complicated init situation at this point in which we need to do the following: 1) Initialize static cm clusters 2) Initialize cds cm clusters 3) Initialize rds 4) Start listening This change sets up a generic init manager framework that allows extensions to initialize after cm init but before we start listening. This commit also adds "integration tests" for CDS/RDS in that we specify them in one of the integration test configs. Nothing is currently implemented but it at least checks that the server initialized correctly. fixes #465
|
@lyft/network-team @rshriram @GregHanson |
RomanDzhabarov
approved these changes
Feb 15, 2017
lizan
pushed a commit
to lizan/envoy
that referenced
this pull request
Apr 24, 2020
implement declare_property
wolfguoliang
pushed a commit
to wolfguoliang/envoy
that referenced
this pull request
Jan 23, 2021
…envoyproxy#482) * zh-translation: docs/root/configuration/listeners/network_filters/mysql_proxy_filter.rst * fix translate
jpsim
pushed a commit
that referenced
this pull request
Nov 28, 2022
This reverts commit 4647e878fa945dcf3a3a38f7159b58f5cd890662. We noticed when building with these new release options that builds fail with the following errors: ``` Uncompressed input jar has size 18446744072925756006, which exceeds the maximum supported output size 4294967295. Assuming that ijar will be smaller and hoping for the best. Target //:ios_dist failed to build ``` Signed-off-by: Michael Rebello <[email protected]> Signed-off-by: JP Simard <[email protected]>
jpsim
pushed a commit
that referenced
this pull request
Nov 29, 2022
This reverts commit 4647e878fa945dcf3a3a38f7159b58f5cd890662. We noticed when building with these new release options that builds fail with the following errors: ``` Uncompressed input jar has size 18446744072925756006, which exceeds the maximum supported output size 4294967295. Assuming that ijar will be smaller and hoping for the best. Target //:ios_dist failed to build ``` Signed-off-by: Michael Rebello <[email protected]> Signed-off-by: JP Simard <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have a fairly complicated init situation at this point in which we need to
do the following:
This change sets up a generic init manager framework that allows extensions to
initialize after cm init but before we start listening.
This commit also adds "integration tests" for CDS/RDS in that we specify them
in one of the integration test configs. Nothing is currently implemented but it
at least checks that the server initialized correctly.
fixes #465