search

rancher / rke

Rancher Kubernetes Engine (RKE), an extremely simple, lightning fast Kubernetes distribution that runs entirely within containers.
Apache License 2.0
3.22k stars 582 forks source link

Add kube-router CNI support #3404

Closed BloodyIron closed 3 weeks ago

BloodyIron commented 1 year ago

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[bot] commented 11 months ago

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 commented 11 months ago

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

github-actions[bot] commented 9 months ago

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 commented 9 months ago

asdf

aauren commented 9 months ago

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: https://github.com/cloudnativelabs/kube-router/issues/1600

BloodyIron commented 9 months ago

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 commented 9 months ago

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

BloodyIron commented 9 months ago

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[bot] commented 7 months ago

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 commented 7 months ago

asdf

github-actions[bot] commented 5 months ago

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 commented 5 months ago

Not stale

github-actions[bot] commented 3 months ago

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 commented 3 months ago

asdf

github-actions[bot] commented 1 month ago

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.

MrBlaise commented 4 days ago

Interested in this too