sarvekshayr commented on code in PR #259: URL: https://github.com/apache/ozone-site/pull/259#discussion_r2706847308
########## docs/05-administrator-guide/02-configuration/03-security/05-encryption/01-network-encryption/02-grpc.md: ########## Review Comment: ```suggestion sidebar_label: gRPC TLS ``` ########## docs/05-administrator-guide/02-configuration/03-security/05-encryption/01-network-encryption/02-grpc.md: ########## @@ -4,4 +4,29 @@ sidebar_label: gRPC # Configuring gRPC With TLS -**TODO:** File a subtask under [HDDS-9859](https://issues.apache.org/jira/browse/HDDS-9859) and complete this page or section. +Ozone traffic may be transferred via gRPC (e.g., Ratis write pipeline or client reading blocks from Datanode). To enable TLS for gRPC traffic, set `hdds.grpc.tls.enabled` to **true**. This encrypts communication between Ozone services that use gRPC. + +## Configuration + +Add the following property to your `ozone-site.xml` configuration file: + +```xml +<property> + <name>hdds.grpc.tls.enabled</name> + <value>true</value> + <description>Enable TLS for gRPC traffic</description> +</property> +``` + +When enabled, this property encrypts: + +- Ratis write pipeline communication +- Client-to-Datanode block read operations +- Other internal gRPC-based communication between Ozone services Review Comment: This seems repetitive as it is already in the description. How about we rephrase the description and add these points followed by the configuration? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
