Kubernetes cluster using kube-router does not pass k8s conformance test

[aceeric]

I created a desktop Kubernetes cluster v1.20.1 with three nodes running in VirtualBox VMs running CentOS 8 guests using bridged networking. I installed kube-router for networking using https://raw.githubusercontent.com/cloudnativelabs/kube-router/v1.1.1/daemonset/generic-kuberouter-all-features.yaml.

I installed Core DNS 1.14.0. I installed and ran a handful of workloads to ensure the cluster was functional, including metrics-server and kubernetes dashboard. I downloaded and ran the Sonobuoy e2e conformance tests:

$ conformance/sonobuoy run\
 --plugin=e2e\
 --sonobuoy-image=projects.registry.vmware.com/sonobuoy/sonobuoy:v0.20.0\
 --mode=certified-conformance\
 --timeout=30000

Using this version of sonobuoy:

$ sonobuoy version --kubeconfig=$KUBECONFIG
Sonobuoy Version: v0.20.0
MinimumKubeVersion: 1.17.0
MaximumKubeVersion: 1.99.99
GitSHA: f6e19140201d6bf2f1274bf6567087bc25154210
API Version:  v1.20.1

Three tests failed. One - [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly] [Conformance] - looked very much like an issue on GitHub that was logged for kube-proxy and resulted in a change there: https://github.com/kubernetes/kubernetes/issues/89358

I asked this question on the kube-router slack channel (https://kubernetes.slack.com/archives/C8DCQGTSB/p1614646488017200) but didn't get a response. My question is: using the kube-router-all-features yaml as described above, is it reasonable to expect to pass the conformance tests?

Thanks