Fix flannel CNI version to use 0.2.0

[srikiz]

This issue occurs when using flannel network provider with the latest master.

This issue is mentioned here - flannel-io/flannel#1178 and it's fix was done few days back as mentioned here - https://github.com/coreos/flannel/pull/1174/files

After creating a v1.16 cluster by kubeadm init and installing flannel cni by kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/32a765fd19ba45b387fdc5e3812c41fff47cfd55/Documentation/kube-flannel.yml, the network still does not get ready and coredns remain pending.

The same issue was observed with latest KOPS master and this PR should fix the issue.
I tested this change on the latest master and it seems to be working fine.

[k8s-ci-robot]

Hi @srikiz. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[rifelpet]

/ok-to-test

[srikiz]

/assign @mikesplain

[mikesplain]

This looks good. Thanks @srikiz!

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mikesplain, srikiz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mikesplain]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[paalkr]

I encountered this issue when creating a fresh 1.16 cluster using kops v1.16.0-beta2. Will this fix get into the next 1.16.0 beta?