Welcome to the Linux Foundation Forum!

Pod Network

Question: Why does Kubernetes lack a pod network?
Details: The materials for Install and Config for the LFS258 class, and Kubernetes.io docs indicate that it's required to use a 3rd party pod networking tool for pod to pod communication among various other communication functionality. Why is this not something that's included with base Kubernetes functionality ?

Comments

  • Networking is so fundamental to everything that I would think that some basic connectivity "out of the box" would be desirable even if it were to get disabled and replaced by something more sophisticated (e.g. calico, etc.) later on.

    Since it seems like running this on a home network using something like KVM or OpenBox virtualization is really common, I am very surprised that the defaults for the class are an entire /16. The other networking defaults in the course files also seems like it creates a lot of 10.0.0.0/8 addresses and and 172.16.0.0/12 so its almost impossible not to have some kind of an overlap.

  • Hi @recentcoin,

    It is true that the default configs are not necessarily designed for smaller size home network setups, but, considering all the flexibility that comes out of the box with all tools mentioned above, network sizes can be easily reconfigured to avoid any such overlaps.

    Regards,
    -Chris

  • Thanks for the response. I understand your point, that Kubernetes is not intended to be a complete and monolithic solution. Similarly, one could ask why doesn't Kubernetes have a container subsystem, but instead uses Docker or CRI-O. Of course it's going to re-use good existing utilities that already exist!

Categories

Upcoming Training