[GitHub] [flink] gaborgsomogyi commented on a diff in pull request #18746: [FLINK-26162][docs]revamp security pages

[GitBox <gi...@apache.org>]

gaborgsomogyi commented on code in PR #18746:
URL: https://github.com/apache/flink/pull/18746#discussion_r849203162


##########
docs/content/docs/security/ssl.md:
##########
@@ -0,0 +1,367 @@
+---
+title: "Encryption and Authentication using SSL/TLS"
+weight: 3
+type: docs
+aliases:
+  - /deployment/security/ssl.html
+  - /ops/security-ssl.html
+---
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# Encryption and Authentication using SSL/TLS for Cluster Components
+
+Flink supports mutual authentication (when two parties authenticate each other at the same time) and 
+encryption of network communication with SSL for internal and external communication. 
+
+**By default, SSL/TLS authentication and encryption is not enabled** (to have defaults work out-of-the-box).
+
+This guide will explain internal vs external connectivity, and provide instructions on how to enable 
+SSL/TLS authentication and encryption for network communication with and between Flink processes. We 
+will go through steps such as generating certificates, setting up TrustStores and KeyStores, and 
+configuring cipher suites.
+
+For how-tos and tips for different deployment environments (i.e. standalone clusters, Kubernetes, YARN),
+check out the section on [Incorporating Security Features in a Running Cluster]({{< ref "docs/security/running-cluster" >}}).
+
+## Internal and External Communication 
+
+There are two types of network connections to authenticate and encrypt: internal and external.
+
+{{< img src="/fig/ssl_internal_external.svg" alt="Internal and External Connectivity" width=75% >}}
+
+For more flexibility, security for internal and external connectivity can be enabled and configured
+separately.
+
+### Internal Connectivity
+
+Flink internal communication refers to all connections made between Flink processes. These include:
+
+- Control messages: RPC between JobManager / TaskManager / Dispatcher / ResourceManager
+- Transfers on the data plane: connections between TaskManagers to exchange data during shuffles, 
+  broadcasts, redistribution, etc
+- Blob service communication: distribution of libraries and other artifacts
+
+All internal connections are SSL authenticated and encrypted. The connections use **mutual authentication**,
+meaning both server and client side of each connection need to present the certificate to each other. 
+The certificate acts as a shared secret and can be embedded into container images or attached to your 
+deployment setup. These connections run Flink custom protocols. Users never connect directly to internal 
+connectivity endpoints.
+
+### External Connectivity
+
+Flink external communication refers to all connections made from the outside to Flink processes. 
+This includes: 
+- communication with the Dispatcher to submit Flink jobs (session clusters)
+- communication of the Flink CLI with the JobManager to inspect and modify a running Flink job/application
+
+These connections are exposed via REST/HTTP endpoints (and are used by Flink's web UI). Some 
+application-specific external services such as sources and sinks may use some other network protocol.
+
+The server will, by default, accept connections from any client, meaning that the REST endpoint does 
+not authenticate the client. These REST endpoints, however, can be configured to require SSL encryption 
+and mutual authentication. 
+
+However, the recommended approach is setting up and configuring a dedicated proxy service (a "sidecar 
+proxy") that controls access to the REST endpoint. This involves binding the REST endpoint to the 
+loopback interface (or the pod-local interface in Kubernetes) and starting a REST proxy that authenticates 
+and forwards the requests to Flink. Examples for proxies that Flink users have deployed are [Envoy Proxy](https://www.envoyproxy.io/) 
+or [NGINX with MOD_AUTH](http://nginx.org/en/docs/http/ngx_http_auth_request_module.html).
+
+The rationale behind delegating authentication to a proxy is that such proxies offer a wide variety
+of authentication options and thus better integration into existing infrastructures.
+
+## Queryable State
+
+Connections to the [queryable state]({{< ref "docs/dev/datastream/fault-tolerance/queryable_state" >}}) 
+endpoints is currently not authenticated or encrypted.
+
+## SSL Setups
+
+{{< img src="/fig/ssl_mutual_auth.svg" alt="SSL Mutual Authentication" width=75% >}}

Review Comment:
   @infoverload I've taken a deeper look and found the issue. The mentioned `svg` file has `html` content. Please save the proper `svg` file into `ssl_mutual_auth.svg` and then everything will work like charm.



-- 
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: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org