Skip to content
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

doc: add TLS related warnings #12060

Merged
merged 1 commit into from
Jun 24, 2020
Merged

doc: add TLS related warnings #12060

merged 1 commit into from
Jun 24, 2020

Conversation

xiang90
Copy link
Contributor

@xiang90 xiang90 commented Jun 23, 2020

Copy link
Member

@spzala spzala left a comment

Choose a reason for hiding this comment

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

Thanks @xiang90 LGTM except that I noticed one typo :-) and so I also had couple other nits.

@@ -103,5 +103,5 @@ $ etcd gateway start --discovery-srv=example.com

#### --trusted-ca-file

* Path to the client TLS CA file for the etcd cluster. Used to authenticate endpoints.
* Path to the client TLS CA file for the etcd cluster to verify the endpoints returned from SRV discovery. Note that it is ONLY used for authenticating the discovered endpoints rather than creating connections for data transfereing. The gateway never terminates TLS connections or create TLS connections on behave of its clients.
Copy link
Member

Choose a reason for hiding this comment

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

Nit - typo :-) transfereing vs transferring Thanks @xiang90

@@ -103,5 +103,5 @@ $ etcd gateway start --discovery-srv=example.com

#### --trusted-ca-file

* Path to the client TLS CA file for the etcd cluster. Used to authenticate endpoints.
* Path to the client TLS CA file for the etcd cluster to verify the endpoints returned from SRV discovery. Note that it is ONLY used for authenticating the discovered endpoints rather than creating connections for data transfereing. The gateway never terminates TLS connections or create TLS connections on behave of its clients.
Copy link
Member

Choose a reason for hiding this comment

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

Also, another nit - should we use "behalf" instead of "behave"?

@@ -4,7 +4,7 @@ title: etcd gateway

## What is etcd gateway

etcd gateway is a simple TCP proxy that forwards network data to the etcd cluster. The gateway is stateless and transparent; it neither inspects client requests nor interferes with cluster responses.
etcd gateway is a simple TCP proxy that forwards network data to the etcd cluster. The gateway is stateless and transparent; it neither inspects client requests nor interferes with cluster responses. It does not terminate TLS connections, do TLS handshakes on behave of its clients, or verify if the connection is secured.
Copy link
Member

Choose a reason for hiding this comment

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

Nit - should we use "behalf" instead of "behave"?

Copy link
Member

@spzala spzala left a comment

Choose a reason for hiding this comment

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

Thanks @xiang90 LGTM

@xiang90 xiang90 merged commit beb5614 into etcd-io:master Jun 24, 2020
@xiang90 xiang90 deleted the doc branch June 24, 2020 04:07
gyuho added a commit that referenced this pull request Jun 25, 2020
…-upstream-release-3.3

Automated cherry pick of #12060
gyuho added a commit that referenced this pull request Jun 25, 2020
…-upstream-release-3.4

Automated cherry pick of #12060
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants