We will handle it asap. Please check the status of this jira https://issues.apache.org/jira/browse/FLINK-32777
On Mon, Aug 7, 2023 at 8:08 PM Xiaolong Wang <xiaolong.w...@smartnews.com> wrote: > Hi, > > I was testing flink-kubernetes-operator in an IPv6 cluster and found out > the below issues: > > *Caused by: javax.net.ssl.SSLPeerUnverifiedException: Hostname >> fd70:e66a:970d::1 not verified:* >> >> * certificate: sha256/EmX0EhNn75iJO353Pi+1rClwZyVLe55HN3l5goaneKQ=* >> >> * DN: CN=kube-apiserver* >> >> * subjectAltNames: [fd70:e66a:970d:0:0:0:0:1, >> 2406:da14:2:770b:3b82:51d7:9e89:76ce, 10.0.170.248, >> c0c813eaff4f9d66084de428125f0b9c.yl4.ap-northeast-1.eks.amazonaws.com >> <http://c0c813eaff4f9d66084de428125f0b9c.yl4.ap-northeast-1.eks.amazonaws.com>, >> ip-10-0-170-248.ap-northeast-1.compute.internal, kubernetes, >> kubernetes.default, kubernetes.default.svc, >> kubernetes.default.svc.cluster.local]* >> > > Which seemed to be related to a known issue > <https://github.com/square/okhttp/issues/7368> of okhttp. > > I'm wondering if there is a plan to support IPv6 for > flink-kubernetes-operator in the near future ? >
