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.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:
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io