Skip to content

Document incremental xDS semantics about resources that do not exist.#9317

Merged
htuch merged 2 commits intoenvoyproxy:masterfrom
markdroth:incremental_xds_does_not_exist_semantics
Dec 12, 2019
Merged

Document incremental xDS semantics about resources that do not exist.#9317
htuch merged 2 commits intoenvoyproxy:masterfrom
markdroth:incremental_xds_does_not_exist_semantics

Conversation

@markdroth
Copy link
Copy Markdown
Contributor

Description: Document incremental xDS semantics about resources that do not exist.
Risk Level: Low
Testing: N/A
Docs Changes: Included in PR
Release Notes: N/A

This attempts to clarify the incremental xDS protocol semantics, as per discussion in #7415 (comment). CC @htuch

Signed-off-by: Mark D. Roth <roth@google.com>
@repokitteh-read-only
Copy link
Copy Markdown

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to api/.

🐱

Caused by: #9317 was opened by markdroth.

see: more, trace.

Copy link
Copy Markdown
Member

@htuch htuch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, appreciate the clarification. I assume Envoy has to handle this correctly due to the way on-demand VHDS will work (@dmitri-d @brian-avery)
/wait

Comment thread api/xds_protocol.rst Outdated
When a resource subscribed to by a client does not exist, the server will send a :ref:`Resource
<envoy_api_msg_Resource>` whose :ref:`name <envoy_api_field_Resource.name>` field matches the
name that the client subscribed to and whose :ref:`resource <envoy_api_field_Resource.resource>`
field is unset.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The motivation here is to avoid having to wait on a timeout (which is basically what happens during warming in Envoy today). Can you add this to the docs?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

Signed-off-by: Mark D. Roth <roth@google.com>
Copy link
Copy Markdown
Member

@htuch htuch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@htuch htuch merged commit fb89269 into envoyproxy:master Dec 12, 2019
@markdroth markdroth deleted the incremental_xds_does_not_exist_semantics branch December 13, 2019 15:45
prakhag1 pushed a commit to prakhag1/envoy that referenced this pull request Jan 3, 2020
…envoyproxy#9317)

Document incremental xDS semantics about resources that do not exist.
Risk Level: Low
Testing: N/A
Docs Changes: Included in PR
Release Notes: N/A

This attempts to clarify the incremental xDS protocol semantics, as per discussion in envoyproxy#7415

Signed-off-by: Mark D. Roth <roth@google.com>
Signed-off-by: Prakhar <prakhar_au@yahoo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants