The ovn-kubernetes endpoint slice controller requires the following in order to run: 1. The kubernetes cluster has enabled endpoint slices 2. The OVN configuration has enabled dual-stack 3. The kubernetes version has the new dual-stack API, that means it is > 1.20 The detection of the kubernetes version fails in the CI, because the library doesn't parse minors versions that are not only numbers, i.e v1.21.0-alpha.1, that are typically all the clusters that run in the CI. We really don't need the 3rd requirement, because the controller can work without dual-stack, so we can go with 1 and 2 for 4.7 and remove the 3rd requirement directly. For 4.8 the goal is to enable the new endpointslice controller by default.
Fix https://github.com/ovn-org/ovn-kubernetes/pull/2049/
This bug was fixed as part of the recent rebase from upstream https://github.com/openshift/ovn-kubernetes/commit/cdabdc3244de873beaac168b7f613f445bdda380
@aojeagar Hi, could you help show the CI job with the endpoint slice controller for ovn-kubernetes for verifying this bug? thanks.
Verified "Starting OVN Service Controller: Using Endpoint Slices" present in CI log files. // We use a level triggered controller to handle services if the cluster // has endpoint slices enabled. if util.UseEndpointSlices(oc.client) { klog.Infof("Starting OVN Service Controller: Using Endpoint Slices") https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.8-e2e-metal-ipi-ovn-dualstack/1377074392177053696 virthost-ostest-test-metalkube-org-5000-localimages-local-release-image-sha256-f041c0db3b115bf248da6a0782410317e80dadbd96692012dc984dac4aa059e8/namespaces/openshift-ovn-kubernetes/pods/ovnkube-master-mqc52/ovnkube-master/ovnkube-master/logs/previous.log 264:2021-03-31T02:25:04.294503531Z I0331 02:25:04.294494 1 ovn.go:312] Starting OVN Service Controller: Using Endpoint Slices virthost-ostest-test-metalkube-org-5000-localimages-local-release-image-sha256-f041c0db3b115bf248da6a0782410317e80dadbd96692012dc984dac4aa059e8/namespaces/openshift-ovn-kubernetes/pods/ovnkube-master-jwntj/ovnkube-master/ovnkube-master/logs/previous.log 889:2021-03-31T02:32:34.791490944Z I0331 02:32:34.791479 1 ovn.go:312] Starting OVN Service Controller: Using Endpoint Slices virthost-ostest-test-metalkube-org-5000-localimages-local-release-image-sha256-f041c0db3b115bf248da6a0782410317e80dadbd96692012dc984dac4aa059e8/namespaces/openshift-ovn-kubernetes/pods/ovnkube-master-jwntj/ovnkube-master/ovnkube-master/logs/current.log 973:2021-03-31T02:40:17.127074364Z I0331 02:40:17.127054 1 ovn.go:312] Starting OVN Service Controller: Using Endpoint Slices
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.2 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:2438