Verified on OCP4.6.0-0.nightly-2020-10-28-001707 over OSP16.1 with OVN-octavia (RHOS-16.1-RHEL-8-20201007.n.0)

Fix is in:

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.6.0-0.nightly-2020-10-28-001707   True        False         5h31m   Cluster version is 4.6.0-0.nightly-2020-10-28-001707

$ oc get pods -n openshift-kuryr
NAME                                READY   STATUS    RESTARTS   AGE
kuryr-cni-962bd                     1/1     Running   1          6h
kuryr-cni-lfkbm                     1/1     Running   4          5h44m
kuryr-cni-scr8g                     1/1     Running   1          6h
kuryr-cni-t5hzc                     1/1     Running   1          6h
kuryr-cni-x7bch                     1/1     Running   3          5h39m
kuryr-cni-x9b42                     1/1     Running   3          5h40m
kuryr-controller-598d4bf657-6gs9g   1/1     Running   5          6h

$ oc rsh -n openshift-kuryr kuryr-controller-598d4bf657-6gs9g head -83 /usr/lib/python3.6/site-packages/kuryr_kubernetes/controller/drivers/utils.py | tail -1
    return pod['spec'].get('hostNetwork', False)

####

Unexpected ports are not created anymore:

$ oc get pods -A -o wide | grep 10.196 | awk '{print $2}' > host-networking-pods 
$ oc get kp -A | grep -f host-networking-pods | wc -l
0

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 (OpenShift Container Platform 4.6.3 bug fix 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/RHBA-2020:4339