Currently, the tests build and run newest k8s available.
This might be the root of conflicts as k8s version in cluster autoscaler is hardcoded and bumped only manually.
Moreover, presubmits on release branches e.g. cluster-autoscaler-release-1.35 also test against newest k8s.