GCE cluster up is failing for k8s-integration tests on k/k master.

[mattcary]

The symptom is that the e2e-up called from the k8s-integration test on k/k master will hang on waiting for nodes to be ready. Node kubelet logs contain an error like the following.

cannot create certificate signing request: certificatesigningrequests.certificates.k8s.io is forbidden: User "kubelet" cannot create resource "certificatesigningrequests" in API group "certificates.k8s.io" at the cluster scope.

And there are additional errors in the kube-addon-manager.log as well.

It appears that the 888.888 git version used in test/k8s-integration/.dockerized-kube-version-defs causes something critical to get removed or not activated, although I haven't been able to figure out what.

This can be temporarily fixed by setting the version there to 1.21+. It would be better to automatically infer the kube version, maybe there is some trickery to be done, or maybe it would be easiest to clone from git rather than just downloading the archive.

[mattcary]

It appears to be due to 3cf9bc547fcd9d3e93bf7ccdbf989fa7d8c32221, which AFAICT makes the handling of api versions more strict when they are removed.

After poking around, I think it will be difficult to get the correct version information from the source archive, and it will probably be easiest to just git clone instead, at least when testing k8s master.

[mattcary]

/cc @saikat-royc
/cc @verult