Add kube-router CNI support

[BloodyIron]

Can we please have kube-router CNI support added already? I want to use kube-router as the CNI in Rancher without having to hack-job it.

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[BloodyIron]

STILL INTERESTED PLEASE DONT REQUIRE I HAVE TO SPAM TO KEEP THIS OPEN!

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[BloodyIron]

asdf

[aauren]

One of the kube-router maintainers here, let me know if there is something that you need from our side in order to help make this happen.

We do have the following issue open that we are actively working with another user of RKE2 to allow kube-router to more easily integrate with RKE2 like other network providers do by installing the plugins when they're missing: cloudnativelabs/kube-router#1600

[BloodyIron]

It's more about the RKE devs "supporting" kube-router that I'm seeking here, so upstream Rancher can then do kube-router CNI stuff, without having to get greasy under the hood.

So not sure if you're directing that at me @aauren or the RKE devs, but that's where I'm coming from. :)

[aauren]

I've got ya. I was directing it at the RKE devs in case they needed the involvement from someone on the project.

[BloodyIron]

I've got ya. I was directing it at the RKE devs in case they needed the involvement from someone on the project.

How generous of you! Yay! :D

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[BloodyIron]

asdf

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[aauren]

Not stale