Docs: add SDS file secret name

[caleblloyd]

I tried to run Example three: certificate rotation for xDS gRPC connection and got the following error:

[2021-02-24 03:37:06.883][1][warning][config] [source/common/config/filesystem_subscription_impl.cc:43] Filesystem config update rejected: Unexpected SDS secret (expecting tls_sds): 

Additionally, Envoy did not serve a TLS Certificate on my Listener Transport Socket

Upon further inspection, it appears that Envoy is looking for a matching secret name in the SDS response. When I added name: tls_sds to the SDS Response in the file, the error went away and the proper TLS Certificate was served on my Listener Transport Socket

Version Information:

envoy  version: f155eaac66fc23cd3e1a7bf5c4ec2309d308dbb1/1.18.0-dev/Clean/RELEASE/BoringSSL

[repokitteh-read-only]

Hi @caleblloyd, welcome and thank you for your contribution.

We will try to review your Pull Request as quickly as possible.

In the meantime, please take a look at the contribution guidelines if you have not done so already.

🐱

Caused by: #15166 was opened by caleblloyd.

see: more, trace.

[caleblloyd]

@tsaarni I see that you wrote the original example in #9359 which used v2 config

Can you review this PR? Is name now required in SDS Response as a part of v3 config?

[tsaarni]

Looks ok to me , but of course the maintainers need to approve instead of me.