Use correct images for alpha and dev builds #865
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/kind failing-test
See failing migration tests, eg https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-gcp-compute-persistent-disk-csi-driver-latest-k8s-master-migration/1456750077849636864.
The migration tests use the dev overlay, which get images from alpha.
The alpha image overlay included some images apparently targeted at windows. However, metadata name doesn't mean anything, and the transformers changed the images on all versions. The csi driver image ends up being a no-op, because the tag is set to the latest build, but the node-driver-registrar change is effective. When the registrar was updated to 2.3.0, the liveness probe was added (and maybe other things); this is incompatible with the 2.1.0 version.
I don't think it's necessary to use special versions for windows at this point anyway. If we do, we'll have to change the image names in the kustomize base so that we can target windows nodes anyway.
/assign @jingxu97
/assign @saikat-royc