Comment by teleforce

1 day ago

Why stop at K3k, should be named K3k3k in order to capture the truly recursive and nested nature of the container-in-container system?

Joking aside I think this can be a great tool in Kubernetes and container eco-system.

Unlike one of the sibling comments that claimed it's a very niche application, or 99.9% deployment will never ever use this nested feature, I beg to differ.

Apart for testing with container-in-container arrangement, it can be a killer application for realistic simulation of network elements as has been utilized in many network simulators including ComNetsEmu and others [1],[2],[3],[4].

[1] Chapter 13 - ComNetsEmu: a lightweight emulator:

https://www.sciencedirect.com/science/chapter/edited-volume/...

[2] ViPMesh: A virtual prototyping framework for IEEE 802.11s wireless mesh networks:

https://ieeexplore.ieee.org/document/7763263

[3] NestedNet: A Container-based Prototyping Tool for Hierarchical Software Defined Networks:

https://ieeexplore.ieee.org/document/9244858

[4] Network Virtualization and Emulation using Docker, OpenvSwitch and Mininet-based Link Emulation: