[
https://issues.apache.org/jira/browse/FLINK-33368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780027#comment-17780027
]
Mihai L Lalescu commented on FLINK-33368:
-
Yes this is a duplicate of the above.
> 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)