You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2023/10/26 10:29:00 UTC

[jira] [Commented] (FLINK-33368) Support for SNI in the Flink Client

    [ https://issues.apache.org/jira/browse/FLINK-33368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779834#comment-17779834 ] 

Martijn Visser commented on FLINK-33368:
----------------------------------------

[~mihai.l.lalescu] Is this a duplicate of FLINK-28520? 

> Support for SNI in the Flink Client
> -----------------------------------
>
>                 Key: FLINK-33368
>                 URL: https://issues.apache.org/jira/browse/FLINK-33368
>             Project: Flink
>          Issue Type: New Feature
>          Components: Command Line Client
>         Environment: Flink Cluster on OpenShift
> VIP requiring SNI 
> Flink client running on a VM
> Flink version 16.2
> Java 8
>            Reporter: Mihai L Lalescu
>            Priority: Major
>
> We have Flink  clusters running on OpenShift behind a VIP that requires SNI (Server Name Information). The Flink client fails to connect to the Job Manager REST API through the VIP due to lack of SNI support in the Client. The connection was using TLS 1.2.
> If required, I can provide Wireshark traces. The TLS 1.2 Client Hello package does not contain any SNI info.
> I have also searched the Flink source code for the netty SniHandler class and I could not find any use of that class. 
> I have not seen any SNI references here
> https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache/flink/runtime/rest/RestClient.java



--
This message was sent by Atlassian Jira
(v8.20.10#820010)