no_proxy ipv6 entries not handled correctly

[shawkins]

Describe the bug

ipv6 entries that appear in the no_proxy list are not checked.

Fabric8 Kubernetes Client version

6.11.0

Steps to reproduce

set NO_PROXY to contain an ipv6 entry 2048::/110

Expected behavior

Addresses within the range should not use a proxy

Runtime

Kubernetes (vanilla)

Kubernetes API Server version

1.25.3@latest

Environment

Linux

Fabric8 Kubernetes Client Logs

No response

Additional context

No response

[shawkins]

@manusa I think we will need this for our next release of Keycloak, so we'll probably need this in Quarkus 3.15.x.

cc @metacosm @vmuzikar

[manusa]

Should we backport the fix to 6.13 then?

(I'm assuming this based on https://github.com/quarkusio/quarkus/blob/7c367ac49c2f617b6e348247d5b219e91a993f34/pom.xml#L72)

[shawkins]

Should we backport the fix to 6.13 then?

Yes, I believe that is still the target release.

[vmuzikar]

We need it in Quarkus 3.20, as IPv6 isn't coming until Keycloak 26.2.

[manusa]

So no back-port + release needed then?

If that's the case, I can prioritize releasing 7.1 (which was the original plan for next week).

Also, @shawkins, I'd need your input for #6792, to see if we need to do something there or leave it as is.

[vmuzikar]

So no back-port + release needed then?

I'm not sure which version Quarkus 3.20, especially JOSDK will use. CC @metacosm

[metacosm]

So no back-port + release needed then?

I'm not sure which version Quarkus 3.20, especially JOSDK will use. CC @metacosm

QOSDK 7 will be used in Quarkus 3.20 (Fabric8 client 7 is used in Quarkus starting with 3.18). QOSDK 7 will use JOSDK 5 which has breaking API changes (though they shouldn't be too difficult to adapt for).