Consider newer topology labels in zone controller

[stoyanr]

This PR adds code to consider the newer topology labels in the zone controller, in addition to the older failure-domain ones. According to https://kubernetes.io/docs/reference/kubernetes-api/labels-annotations-taints/, starting in v1.17, the failure-domain.beta.kubernetes.io/region label is deprecated in favor of topology.kubernetes.io/region, and the failure-domain.beta.kubernetes.io/zone label is deprecated in favor of topology.kubernetes.io/zone.

Since the cloud provider still vendors Kubernetes 1.16, the newer labels of the underkube nodes will be considered when determining the region and zone, but not actually added to the overkube nodes (as this is done by the vendored code). Vendoring a newer Kubernetes version is unfortunately close to impossible since kubevirt.io/client-go is still based on 1.16 and there are conflicts, see also #10.

[stoyanr]

/cc @afritzler @gonzolino

[kubevirt-bot]

@stoyanr: GitHub didn't allow me to request PR reviews from the following users: afritzler.

Note that only kubevirt members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @afritzler @gonzolino

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[stoyanr]

@gonzolino The Travis build fails with:

go: error loading module requirements
Makefile:25: recipe for target 'clean' failed

I don't think this failure has anything to do with my changes. I would like to retrigger the build, but I don't seem to be able to do this from Travis. Is there a way?

[stoyanr]

/retest

[gonzolino]

I couldn't reproduce the travis error on my local machine...

Please adress the comment from teh review, then we can trigger a retest. It's probably just some error on travis.