[flannel] Update from 0.22.0 to 0.26.5

[mkl262]

What type of PR is this?
/kind feature

What this PR does / why we need it:
This PR updates
Which issue(s) this PR fixes:
None

Special notes for your reviewer:

Does this PR introduce a user-facing change?:
Yes

This update adds 2 variables to flannel:
1. `flannel_enable_nftables` - If set to true, flannel uses nftables instead of iptables to masquerade the traffic. Defaults to false
2.`flannel_daemonset_arch_list` - list of architecture specific Daemonsets to be created, only amd64 by default.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mkl262 / name: Michael Kanchuker (5a90a9f, 9bd0a78, b236e3b)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mkl262
Once this PR has been reviewed and has the lgtm label, please assign ant31 for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Welcome @mkl262!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @mkl262. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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-sigs/prow repository.

[tico88612]

/ok-to-test

[tico88612]

@mkl262 Could you make your release-note briefly? (You put your current release-note in the commit content.)

[mkl262]

@tico88612 Im not sure I understand what you meant.
Also, I see that CI failes because of a timeout waiting for /run/flannel/subnet.env, but I dont see this issue in my tests, could it happen because I removed custom flannel image repos from tests/common_vars.yml file?

[tico88612]

Im not sure I understand what you meant.

Release note is minimized to one line as much as possible (this will be in the Release description), and I don't think you need to update the magnitude to multiple lines.

These details should be put in docs/ or roles/network_plugin/flannel/defaults/main.yml.

Also, I see that CI failes because of a timeout waiting for /run/flannel/subnet.env, but I dont see this issue in my tests, could it happen because I removed custom flannel image repos from tests/common_vars.yml file?

Nope, because CI tests are frequent, this will trigger a rate limit if DockerHub is used.
@yankay Could you help me upload the new verison of Flannel? Thanks!

[tico88612]

/retest-failed

[tico88612]

/retest

[ant31]

Hi, could you rebase master ?

[mkl262]

@tico88612 @ant31
Done

[tico88612]

Please fix your pre-commit error message and these reviews.

[mkl262]

@tico88612 Done, who can push the updated images to the kubespray repository?

[mkl262]

@tico88612 @yankay Can you please push the image?

[yankay]

@tico88612 @yankay Can you please push the image?

My pleasure, It has been pushed.
/retest

[mkl262]

@yankay @tico88612 Is there a way to see container logs? I cant recreate the issue.

[tico88612]

@mkl262 Click the failing job, you can see that all the checks fail except kub-3. Maybe the template needs to be modified?
https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/9587738496

[tico88612]

/retitle [flannel] Update from 0.22.0 to 0.26.5