Backport of fix(connect): set initial_fetch_time to wait indefinitely into release/1.1.x #206
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.
Backport
This PR is auto-generated from #140 to be assessed for backporting due to the inclusion of the label backport/1.1.
The below text is copied from the body of the original PR.
Description
Attempt 2 at closing hashicorp/consul#17283
Because we use the default initial_fetch_timeout in the Envoy bootstrap, not all Envoy resources may be loaded in busy systems. However, we previously relied on the timeout to start ingress and API gateways. This PR changes the default initial_fetch_timeout to wait indefinitely "0s".
The Consul PR that updates the snapshot functionality is below.
Links
Consul PR
Overview of commits