trevor-dolby-at-ibm-com
commented
11 months ago @kaolaaz163 I hit the same issue with my 4.14.2 single-node cluster and was able to get the operator working by using the release-4.14 branch from this repo and deploying using the development instructions. I was trying to follow the guide at https://www.opensourcerers.org/2023/08/21/quick-start-to-smallest-openshift-cluster-for-windows-workload/ when I hit the issue you describe.
Approximate summary of steps on Ubuntu 22 WSL2 with Docker:
git clone --recurse-submodules -b release-4.14 https://github.com/openshift/windows-machine-config-operator.git
export OPENSHIFT_CI=false
export KUBE_SSH_KEY_PATH=/somewhere/windowskey
export OPERATOR_IMAGE=quay.io/some_user/wmco:test-4.14-1
cd windows-machine-config-operator
sudo ln -s /usr/bin/docker /usr/local/bin/podman
make base-img
make wmco-img IMG=$OPERATOR_IMAGE
docker push quay.io/some_user/wmco:test-4.14-1
hack/olm.sh run -k $KUBE_SSH_KEY_PATHThe scripts use podman but docker works fine also, and the install is very easy once you get the right source level. I used the current release-4.14 branch but the exact git commit was
commit 9456533c6d17c741e3f79c32613d4a1cdad6cf74 (HEAD -> release-4.14, origin/release-4.14)The blog post linked above describes all the necessary steps, and I was very impressed by the ease of use for this operator, both in terms of running it and also building it. Thank you to the people who wrote up the developer docs!
mansikulkarni96
kaolaaz163
tdolby-at-uk-ibm-com
jrvaldes
openshift-bot
openshift-ci[bot]
Attention
Version
OKD
Cluster Version
4.14.0-0.okd-2023-11-14-101924
Platform
Platform agnostic (type=none)
Proxy
No
WMCO Version
6.0.0
Windows version
2019
What happened?
When deploying WMCO through OperatorHub in the deployed OKD 4.14 cluster, only the WMCO 6.0.0 version is seen. When deploying WMCO in a cluster, the following error is reported when WMCO's Pod starts.
failed to validate required cluster configuration {"error": "error validating k8s version: Unsupported server version: v1.27.1-3351+b49f9d1356bca4-dirty. Supported versions are v1.24.x to v1.25.x", "errorVerbose": "Unsupported server version: v1.27.1-3351+b49f9d1356bca4-dirty. Supported versions are v1.24.x to v1.25.x\ngithub.com/openshift/windows-machine-config-operator/pkg/cluster.(config).validateK8sVersion\n\t/build/windows-machine-config-operator/pkg/cluster/config.go:141\ngithub.com/openshift/windows-machine-config-operator/pkg/cluster.(config).Validate\n\t/build/windows-machine-config-operator/pkg/cluster/config.go:148\nmain.main\n\t/build/windows-machine-config-operator/cmd/operator/main.go:102\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1571\nerror validating k8s version\ngithub.com/openshift/windows-machine-config-operator/pkg/cluster.(*config).Validate\n\t/build/windows-machine-config-operator/pkg/cluster/config.go:150\nmain.main\n\t/build/windows-machine-config-operator/cmd/operator/main.go:102\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1571"}
What did you expect to happen?
WMCO can run successfully
Steps to reproduce the issue
Install OKD version 4.14 and deploy WMCO through OperatorHub
Do you have a workaround for this issue?
No response