Description of problem: The current version of openshift/router vendors Kubernetes 1.23 packages. OpenShift 4.11 is based on Kubernetes 1.24. OpenShift release version: 4.11. Steps to Reproduce (in detail): 1. Check <https://github.com/openshift/router/blob/release-4.11/go.mod>. Actual results: Kubernetes packages (k8s.io/api, k8s.io/apimachinery, and k8s.io/client-go) are at version v0.23.0. Expected results: Kubernetes packages are at version v0.24.0 or later. Impact of the problem: Using old Kubernetes API and client packages brings risk of API compatibility issues.
Verified it with 4.11.0-0.nightly-2022-06-15-222801 1. % oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.nightly-2022-06-15-222801 True False 29m Cluster version is 4.11.0-0.nightly-2022-06-15-222801 % 2. % oc rsync -n openshift-ingress $(oc get pods -n openshift-ingress --no-headers | grep "^router-default" | grep Running | head -1 | awk '{print $1}'):/usr/bin/openshift-router . receiving file list ... done openshift-router % 3. % strings ./openshift-router >> forbug.txt % 4. can see k8s.io/api is v0.24.1, k8s.io/apimachinery is v0.24.1, k8s.io/apiserver is v0.24.1 and k8s.io/client-go is v0.24.1 by the below grep command % grep -B1 "v0.24.1" forbug.txt k8s.io/api <-- v0.24.1 k8s.io/apimachinery <-- v0.24.1 k8s.io/apiserver. <-- v0.24.1 k8s.io/client-go <-- v0.24.1 k8s.io/component-base v0.24.1 -- k8s.io/api v0.24.1 k8s.io/apimachinery v0.24.1 k8s.io/apiserver v0.24.1 k8s.io/client-go v0.24.1 k8s.io/component-base v0.24.1 %
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 (Important: OpenShift Container Platform 4.11.0 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-2022:5069