Add Flannel support for multi-arch deployments

[bshephar]

What would you like to be added:
Add support for a arm64 daemonset so that Flannel works on Raspberry Pis (Or other ARM64 devices) in multi-arch environments

Why is this needed:
If you're running some nodes on x86_64, and then add some ARM nodes, there is no daemonset created for Flannel to use the arm64 image. This means the new nodes are left in NotReady state until the daemonset is created for flannel pointing to the ARM64 image.

We just need to copy the existing template and create the manifest for it during the deployment.

╰─ k get nodes
NAME                           STATUS     ROLES          AGE   VERSION
k8s-master0.k8s.bne-home.net   Ready      master         8d    v1.19.1
k8s-master1.k8s.bne-home.net   Ready      master         8d    v1.19.1
k8s-master2.k8s.bne-home.net   Ready      master         8d    v1.19.1
k8s-node1.k8s.bne-home.net     Ready      ovirt,worker   8d    v1.19.1
k8s-node2.k8s.bne-home.net     Ready      ovirt,worker   8d    v1.19.1
k8s-node3.k8s.bne-home.net     NotReady   rpi,worker     30h   v1.19.1

Once a daemonset is created for it and the deployment re-run, the node comes online. The daemonset I have just used the same template you already had, but copied it and added the arm64 image instead. The result:

╰─ k get ds
NAME                 DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-flannel         5         5         5       5            5           <none>                   9d
kube-flannel-arm64   1         1         1       1            1           <none>                   22h

We could probably use the same template though and just add some Jinja2 logic to it. But for now, I've just copied the template. I'll send you a pull request and we can discuss the best way to implement it if you would like to have this feature.

[floryut]

@bshephar Is this what you are looking for #6166 ?

[r3d3mpt10n]

Hey, yeah. That's what I was looking for. Not sure why I missed that one.

Cheers, lets go ahead and close this one off then. That one seems to cover all of it.

[floryut]

Neat, happy that it fit your needs :)

/close

[k8s-ci-robot]

@floryut: Closing this issue.

In response to this:

Neat, happy that it fit your needs :)

/close

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.