Describe the bug
I'm not sure if this is a bug or intended behavior:
the oc binary provided by the current downloads deployment in the openshift-console namespace self-reports to be version v4.2.0-alpha.0-2827-g19a2243
In fact, from what I can test easily, all the binaries in quay.io/okd/scos-content@sha256:e6d447e8fa1da8b188aaf020d9b409a7287ba5aa01dae7b10b6213ef698a5aaf seem to report that exact version.
Version
4.21.0-okd-scos.1
Reproducibility
100%
Log Bundle
$ oc version
Client Version: v4.2.0-alpha.0-2827-g19a2243
Kustomize Version: v5.7.1
Server Version: 4.21.0-okd-scos.1
Kubernetes Version: v1.34.2-dirty
Describe the bug
I'm not sure if this is a bug or intended behavior:
the
ocbinary provided by the currentdownloadsdeployment in theopenshift-consolenamespace self-reports to be versionv4.2.0-alpha.0-2827-g19a2243In fact, from what I can test easily, all the binaries in
quay.io/okd/scos-content@sha256:e6d447e8fa1da8b188aaf020d9b409a7287ba5aa01dae7b10b6213ef698a5aafseem to report that exact version.Version
4.21.0-okd-scos.1
Reproducibility
100%
Log Bundle