-
Notifications
You must be signed in to change notification settings - Fork 267
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: add cluster warming information #541
Conversation
Signed-off-by: Matt Klein <[email protected]>
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.
Approved, will leave it for you to merge when the Envoy-side PR is merged.
--------------- | ||
|
||
When clusters are initialized both at server boot as well as via CDS, they are "warmed." This means | ||
that clusters do not become available until the following operations have taken place. |
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.
It is not immediately clear what availability implies.. Does cluster unavailability imply that:
- routes that reference the cluster fail
validate_clusters
check, and - listeners that reference the cluster remain in the warming state?
Signed-off-by: Matt Klein <[email protected]>
@kyessenov updated. Better? |
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. This makes it clear what availability means for clusters.
Signed-off-by: Matt Klein [email protected]