Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

It's time to decide which CNI version to use for v1.8.
We should do early in the cycle to catch regressions in the CNI <-> k8s integration.
We don't want the thing that happened in v1.6 to occur again, so we need to be very careful.

Currently, we're using v0.5.1 and consuming tarballs via a sha pushed by this Makefile: https://github.com/kubernetes/kubernetes/blob/master/build/cni/Makefile

We did this earlier because CNI didn't provide binary artifacts for all platform that kubernetes supports.
Since v0.5.2, they do, so we can get rid of build/cni/Makefile 🎉

Also, we don't want to consume a strange SHA as the version indicator, instead we want to use a version number and possibly a SHA for verification.

I guess it would make sense to bump CNI to v0.5.2 for the v1.8 cycle.
Agree/disagree? It's not clear to me when v0.6.0 will be released, but the rc has been out for some time already...

cc @kubernetes/sig-network-feature-requests @ixdy @freehan @kubernetes/sig-cluster-lifecycle-feature-requests @dcbw