-
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
docs: clarify xds docs with warming information #6236
Conversation
Signed-off-by: Rama Chavali <rama.rao@salesforce.com>
@mattklein123 @htuch PTAL |
Signed-off-by: Rama Chavali <rama.rao@salesforce.com>
api/XDS_PROTOCOL.md
Outdated
go through `warming` before they can serve requests. This process happens both during | ||
[`Envoy initialization`](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/init.html#initialization) | ||
and when the `Cluster` or `Listener` is updated. Warming of `Cluster` is completed only when a | ||
`ClusterLoadAssignment` response is supplied by management server. Similarly warming of `Listener` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: s/Similarly/Similarly,
api/XDS_PROTOCOL.md
Outdated
[`Envoy initialization`](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/init.html#initialization) | ||
and when the `Cluster` or `Listener` is updated. Warming of `Cluster` is completed only when a | ||
`ClusterLoadAssignment` response is supplied by management server. Similarly warming of `Listener` | ||
is completed only when a `RouteConfiguration` is suppled by management server if the listener |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: remove extra space after `RouteConfiguration`
api/XDS_PROTOCOL.md
Outdated
and when the `Cluster` or `Listener` is updated. Warming of `Cluster` is completed only when a | ||
`ClusterLoadAssignment` response is supplied by management server. Similarly warming of `Listener` | ||
is completed only when a `RouteConfiguration` is suppled by management server if the listener | ||
refers to an RDS configuration. Management Server is expected to provide the EDS/RDS updates during |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: s/Server/server
api/XDS_PROTOCOL.md
Outdated
is completed only when a `RouteConfiguration` is suppled by management server if the listener | ||
refers to an RDS configuration. Management Server is expected to provide the EDS/RDS updates during | ||
warming. If management server does not provide EDS/RDS information, Envoy will not initialize | ||
it self during initialization phase and the updates sent via CDS/LDS will not take effect till |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/it self/itself
Signed-off-by: Rama Chavali <rama.rao@salesforce.com>
/retest |
🔨 rebuilding |
/retest |
🔨 rebuilding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM modulo nit. Thanks!
api/XDS_PROTOCOL.md
Outdated
is completed only when a `RouteConfiguration` is suppled by management server if the listener | ||
refers to an RDS configuration. Management server is expected to provide the EDS/RDS updates during | ||
warming. If management server does not provide EDS/RDS responses, Envoy will not initialize | ||
itself during initialization phase and the updates sent via CDS/LDS will not take effect till |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drop "during initialization phase"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was in two minds when I wrote this - but decided to add this for more clarity. LMK if you strong feel about removing, I can remove.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Up to you. I don't feel too strongly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this, will defer to @htuch on the full review.
As an aside, I think we should migrate this MD file into the sphinx docs where they will be more discoverable, we can ref link, etc. If people agree can we open an issue to track that?
api/XDS_PROTOCOL.md
Outdated
[`Envoy initialization`](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/init.html#initialization) | ||
and when the `Cluster` or `Listener` is updated. Warming of `Cluster` is completed only when a | ||
`ClusterLoadAssignment` response is supplied by management server. Similarly, warming of `Listener` | ||
is completed only when a `RouteConfiguration` is suppled by management server if the listener |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: s/suppled/supplied/
api/XDS_PROTOCOL.md
Outdated
is completed only when a `RouteConfiguration` is suppled by management server if the listener | ||
refers to an RDS configuration. Management server is expected to provide the EDS/RDS updates during | ||
warming. If management server does not provide EDS/RDS responses, Envoy will not initialize | ||
itself during initialization phase and the updates sent via CDS/LDS will not take effect till |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: "the initialization phase", s/till/untill/
Signed-off-by: Rama Chavali <rama.rao@salesforce.com>
@htuch addressed review comments. PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
* master: (59 commits) http fault: add response rate limit injection (envoyproxy#6267) xds: introduce initial_fetch_timeout option to limit initialization time (envoyproxy#6048) test: fix cpuset-threads tests (envoyproxy#6278) server: add an API for registering for notifications for server instance life… (envoyproxy#6254) remove remains of TestBase (envoyproxy#6286) dubbo_proxy: Implement the routing of Dubbo requests (envoyproxy#5973) Revert "stats: add new BoolIndicator stat type (envoyproxy#5813)" (envoyproxy#6280) runtime: codifying runtime guarded features (envoyproxy#6134) mysql_filter: fix integration test flakes (envoyproxy#6272) tls: update BoringSSL to debed9a4 (3683). (envoyproxy#6273) rewrite buffer implementation to eliminate evbuffer dependency (envoyproxy#5441) Remove the dependency from TimeSystem to libevent by using the Event::Scheduler abstraction as a delegate. (envoyproxy#6240) fuzz: fix use of literal in default initialization. (envoyproxy#6268) http: add HCM functionality required for rate limiting (envoyproxy#6242) Disable mysql_integration_test until it is deflaked. (envoyproxy#6250) test: use ipv6_only IPv6 addresses in custom cluster integration tests. (envoyproxy#6260) tracing: If parent span is propagated with empty string, it causes th… (envoyproxy#6263) upstream: fix oss-fuzz issue envoyproxy#11095. (envoyproxy#6220) Wire up panic mode subset to receive updates (envoyproxy#6221) docs: clarify xds docs with warming information (envoyproxy#6236) ...
Signed-off-by: Rama Chavali rama.rao@salesforce.com
Description: As a follow-up to #6151 , this PR updates xds docs.
Risk Level: Low
Testing: N/A
Docs Changes: N/A
Release Notes: N/A