Evaluate Container Networking Interface with Quilkin #409
Labels
area/networking
Related to networking I/O
area/user-experience
Pertaining to developers trying to use Quilkin, e.g. cli interface, configuration, etc
kind/design
Proposal discussing new features / fixes and how they should be implemented
kind/feature
New feature or request
priority/low
Issues that don't need to be addressed in the near term.
Last month the "Container Networking Interface" was stabilised. CNI plugins allow for cloud vendor agnostic networking between nodes, and provides plugin functionality, allowing applications to extend networking behaviour. We should look into and evaluate having a CNI plugin for Quilkin, what features it should have, and how it should behave. This has the potential to cover a lot of the network optimisations and integrations. For example, integrating with the Firewall CNI plugin, would allow Quilkin to integrate with both
firewalld
andiptables
, as they're both compatible CNI firewall backends.The text was updated successfully, but these errors were encountered: