Much like with storage, the world of container networking is still a relatively emergent space. That being said, the landscape is not completely devoid of tools. Jon Langemak wrote up a look at the Container Networking interface, going over some basic configuration and setup. Somewhat confusingly, this can work with Docker’s Container Network Model, but not out of the box.
This is a pretty introductory overview, so if you’ve ever wanted to delve into container networking, Jon’s piece makes it easy. He’s planning a follow up that will go into more details on setting up some CNI plugins, so stay tuned to follow his journey in this interesting space.
Das Blinken Lichten comments:
If you’ve been paying attention to the discussions around container networking you’ve likely heard the acronym CNI being used. CNI stands for Container Networking Interface and it’s goal is to create a generic plugin-based networking solution for containers. CNI is defined by a spec (read it now, its not very long) that has some interesting language in it.
Read more at: Understanding CNI (Container Networking Interface)
- TELoIP and the SD-WAN Cook-off - April 21, 2017
- The Future of On-Prem in a Cloud World - April 21, 2017
- Rook is the New Flocker? - April 21, 2017
- Virtualization and Containers: All of This Has Happened Before - April 11, 2017
- TCP Terminators: An Expert Analysis - April 11, 2017
- Qumulo Secures Round C Prime Funding – My Conversation with Bill Richter - April 11, 2017
- CapEx on Cloud up 22% in 2016 - April 10, 2017
- IPv6 Hits the Weekend, Network Engineers are Programmers, and Epoch Rollover Considerations in Gestalt Networking News 17.5 - April 7, 2017
- Remembering the IBM 1403: Hammer Time - April 5, 2017
- AWS Coming to Sweden in 2018 - April 4, 2017