Deprecation announcement for CNI plugins
Folks, I wrote a short blog about Podman adding a deprecation announcement for CNI plugins. With the success of the new network stack, not only do we eventually want the new stack to be the default but also the only option. For more information, check out the blog post itself: https://blog.podman.io/2023/01/podman-begins-cni-plugins-deprecation/
Right now, the CNI plugins are the only option for networking on FreeBSD. The new stack seems very exciting though and FreeBSD has recently added netlink support so porting it seems quite possible (and is probably a good excuse to learn a bit of rust). On Tue, 10 Jan 2023 at 13:31, Brent Baude <bbaude@redhat.com> wrote:
Folks,
I wrote a short blog about Podman adding a deprecation announcement for CNI plugins. With the success of the new network stack, not only do we eventually want the new stack to be the default but also the only option. For more information, check out the blog post itself:
https://blog.podman.io/2023/01/podman-begins-cni-plugins-deprecation/ _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Doug, Well the good thing is I know some of the authors of rust code :) And we arent going anywhere. On Tue, Jan 10, 2023 at 7:43 AM Doug Rabson <dfr@rabson.org> wrote:
Right now, the CNI plugins are the only option for networking on FreeBSD. The new stack seems very exciting though and FreeBSD has recently added netlink support so porting it seems quite possible (and is probably a good excuse to learn a bit of rust).
On Tue, 10 Jan 2023 at 13:31, Brent Baude <bbaude@redhat.com> wrote:
Folks,
I wrote a short blog about Podman adding a deprecation announcement for CNI plugins. With the success of the new network stack, not only do we eventually want the new stack to be the default but also the only option. For more information, check out the blog post itself:
https://blog.podman.io/2023/01/podman-begins-cni-plugins-deprecation/ _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
The only objection was that we didn't want to have two network stacks for minikube, since we were already using CNI for kubernetes (with CRI-O) Also didn't want to add a Rust toolchain. But for now using Podman 3.4 will work for a while yet, and I guess it is inevitable considering conmon-rs.... For our limited use case of "podman build", --network=host also works ? At least they don't have to fight over /etc/cni/net.d directory, anymore :-) /Anders Den tis 10 jan. 2023 kl 14:30 skrev Brent Baude <bbaude@redhat.com>:
Folks,
I wrote a short blog about Podman adding a deprecation announcement for CNI plugins. With the success of the new network stack, not only do we eventually want the new stack to be the default but also the only option. For more information, check out the blog post itself:
https://blog.podman.io/2023/01/podman-begins-cni-plugins-deprecation/
On 1/10/23 08:44, Anders F Björklund wrote:
The only objection was that we didn't want to have two network stacks for minikube, since we were already using CNI for kubernetes (with CRI-O)
Also didn't want to add a Rust toolchain. But for now using Podman 3.4 will work for a while yet, and I guess it is inevitable considering conmon-rs....
For our limited use case of "podman build", --network=host also works ?
At least they don't have to fight over /etc/cni/net.d directory, anymore :-)
/Anders
We are not dropping CNI right away, we are just announcing it so that we don't need to ship it in RHEL10 and Fedora 39. So Podman 4.4 and later will continue to have CNI support for a while yet.
Den tis 10 jan. 2023 kl 14:30 skrev Brent Baude <bbaude@redhat.com>:
Folks,
I wrote a short blog about Podman adding a deprecation announcement for CNI plugins. With the success of the new network stack, not only do we eventually want the new stack to be the default but also the only option. For more information, check out the blog post itself:
https://blog.podman.io/2023/01/podman-begins-cni-plugins-deprecation/
_______________________________________________ Podman mailing list --podman@lists.podman.io To unsubscribe send an email topodman-leave@lists.podman.io
Currently it is using Podman 3.4.2, due to still using Ubuntu 20.04... There were some ugly crashes with that when rebuilt with go1.19, so the ISO (only) is being updated to 3.4.7 (end of the line?). /Anders Den tis 10 jan. 2023 kl 20:59 skrev Daniel Walsh <dwalsh@redhat.com>:
Also didn't want to add a Rust toolchain. But for now using Podman 3.4 will work for a while yet, and I guess it is inevitable considering conmon-rs....
We are not dropping CNI right away, we are just announcing it so that we don't need to ship it in RHEL10 and Fedora 39. So Podman 4.4 and later will continue to have CNI support for a while yet.
Hi,
I wrote a short blog about Podman adding a deprecation announcement for CNI plugins. With the success of the new network stack, not only do we eventually want the new stack to be the default but also the only option. For more information, check out the blog post itself:
are macvlan bridged containers with netavark possible now, without specifying an extra subnet for IPv4 and IPv6? Regards Bjoern
participants (5)
-
Anders F Björklund -
Bjoern Franke -
Brent Baude -
Daniel Walsh -
Doug Rabson