Hi Gyula, Pls clarify if I get this right.
It seems now we are able to configure the httpclient used by fabric8 with the fabric8.httpclient.impl property here: https://github.com/apache/flink-kubernetes-operator/blob/c821b48a75c601c3a64bc03bfbada218a68a0e0d/pom.xml#L117 So we can choose another implementation instead of okhttp, that's supposed to be free of the original issue. Is this correct? Thanks, Attila On Mon, 16 Dec 2024 at 16:46, Gyula Fóra <gyula.f...@gmail.com> wrote: > Hi! > > I think the ticket is closed somewhat incorrectly as the okhttp version was > never upgraded. > However now it's possible to switch the httpclient to > different implementations since 1.10, so probably for ipv6 that would work. > > Cheers, > Gyula > > On Mon, Dec 16, 2024 at 4:42 PM Attila Kreiner <kreiner.att...@gmail.com> > wrote: > > > Hello Community, > > > > Our team just found this note about IPv6 in the operator docs: > > > > > > > https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/operations/configuration/#ipv6-configuration > > > > If you run Flink Operator in IPV6 environment, the host name verification > > > error will be triggered due to a known bug in Okhttp client. [...] > > > > > > It links to this jira ticket > > https://issues.apache.org/jira/browse/FLINK-32777 which seems to be > > fixed/closed in 1.7. > > > > Can someone pls confirm if this is just a stale comment? In this case I'd > > be happy to open a PR to remove it. > > > > Thanks, > > Attila > > >
