kuma-cp: SDS server should support DiscoveryRequests with an empty list of resource names #337
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
…st of resource names
| if len(req.ResourceNames) == 0 { | ||
| // Do not respond to SDS requests with an empty list of resource names. | ||
| // In practice, such requests can be observed when Envoy is removing | ||
| // Listeners and Clusters with TLS configuration that refers to SDS. |
There was a problem hiding this comment.
👍 for the comment explaining why
jakubdyszkiewicz
approved these changes
Oct 11, 2019
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.
Summary
SDSserver should supportDiscoveryRequestswith an empty list of resource namesIssues resolved
Fix #328