Verified in "4.8.0-0.ci.test-2021-07-28-122806-ci-ln-1kfykdt-latest" version. With this version, it is observed that the ipv6 whitelist configuration gets added in the router backend for which the annotation is applied: ------ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.ci.test-2021-07-28-122806-ci-ln-1kfykdt-latest True False 29m Cluster version is 4.8.0-0.ci.test-2021-07-28-122806-ci-ln-1kfykdt-latest oc get route service-unsecure -o yaml apiVersion: route.openshift.io/v1 kind: Route metadata: annotations: haproxy.router.openshift.io/ip_whitelist: 2600:14a0::/40 openshift.io/host.generated: "true" creationTimestamp: "2021-07-28T13:38:06Z" labels: name: service-unsecure name: service-unsecure namespace: test1 resourceVersion: "47701" uid: eab5deed-967b-4d02-a278-f4b986a9dcf0 haproxy pod: backend be_http:test1:service-unsecure mode http option redispatch option forwardfor balance acl whitelist src 2600:14a0::/40 tcp-request content reject if !whitelist <----- ------
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.4 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2983