Description of problem: OpenShift 4.6 clusters are reporting kube version 1.17 causing issues for projects/operatirs that are tied to kube versions. Example CI failure due to this: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_windows-machine-config-operator/81/pull-ci-openshift-windows-machine-config-operator-master-e2e-operator/1285712496413380608 2020-07-22T00:24:26.142Z ERROR cmd failed to validate required cluster configuration {"error": "error validating k8s version: Unsupported server version: v1.17.0-alpha.0.7867+649a587b0a0f5d-dirty. Supported version is v1.18.x", "errorVerbose": "Unsupported server version: v1.17.0-alpha.0.7867+649a587b0a0f5d-dirty. Supported version is v1.18.x\nmain.(*clusterConfig).validateK8sVersion\n\t/build/windows-machine-config-operator/cmd/manager/main.go:310\nmain.(*clusterConfig).validate\n\t/build/windows-machine-config-operator/cmd/manager/main.go:319\nmain.main\n\t/build/windows-machine-config-operator/cmd/manager/main.go:106\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1357\nerror validating k8s version\nmain.(*clusterConfig).validate\n\t/build/windows-machine-config-operator/cmd/manager/main.go:321\nmain.main\n\t/build/windows-machine-config-operator/cmd/manager/main.go:106\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1357"} How reproducible: Always Steps to Reproduce: 1. Bring up a 4.6 cluster 2. Try running an operator like WMCO that is tied to a kube version Actual results: Operator fails kube version check Expected results: Operator should run successfully
The reported issue was fixed for CI builds shortly after reporting by the action of pushing upstream tags to the openshift/kubernetes master branch. So long as the tags are synchronized the hyperkube build will use the tag of the most recent rebase level. ART builds are still versioned incorrectly - using an origin version (e.g. 4.x) instead of a kube version (e.g. 1.xx) - and that issue is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1861097