a network Diagram for the VirtualBox

[deepdad]

Please add a network Diagram for the VirtualBox based minikube to the readme.

[afbjorklund]

Would be nice to have, most of it is the standard machine networking (thus #4829)

Basically there is the eth0 (nat) and the eth1 (hostonly), plus loopback and docker.

https://www.virtualbox.org/manual/ch06.html#networkingmodes

https://docs.docker.com/v18.09/network/bridge/

The NAT is mostly used for port forwarding SSH, in order to control the machine VM.

Not sure if this will fit in the README, but should probably be in the documentation...

                         _             _            
            _         _ ( )           ( )           
  ___ ___  (_)  ___  (_)| |/')  _   _ | |_      __  
/' _ ` _ `\| |/' _ `\| || , <  ( ) ( )| '_`\  /'__`\
| ( ) ( ) || || ( ) || || |\`\ | (_) || |_) )(  ___/
(_) (_) (_)(_)(_) (_)(_)(_) (_)`\___/'(_,__/'`\____)

$ ifconfig
docker0   Link encap:Ethernet  HWaddr 02:42:81:00:46:60  
          inet addr:172.17.0.1  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0      Link encap:Ethernet  HWaddr 08:00:27:8C:1A:95  
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe8c:1a95/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:377653 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20671 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:561175082 (535.1 MiB)  TX bytes:1421175 (1.3 MiB)

eth1      Link encap:Ethernet  HWaddr 08:00:27:92:93:B7  
          inet addr:192.168.99.100  Bcast:192.168.99.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe92:93b7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:53 errors:0 dropped:0 overruns:0 frame:0
          TX packets:71 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:5069 (4.9 KiB)  TX bytes:4960 (4.8 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:3042 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3042 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:818746 (799.5 KiB)  TX bytes:818746 (799.5 KiB)

[medyagh]

This could be added to advanced or reference section of minikube site. if anyone interested to add I would accept to review the PR !

@deepdad ?

[afbjorklund]

@medyagh are there any graph tools available ? or should we just go for the image ?

Previously I've mostly used Graphviz, but I'm not sure how advanced this needs to be...

[afbjorklund]

Nice tools:

• LibreOffice Draw
  https://www.libreoffice.org/discover/draw/

• VRT Network Equipment
  https://extensions.libreoffice.org/extensions/vrt-network-equipment

Diagram time!

[medyagh]

@afbjorklund

I am open to any tool, if you are asking for tools to edit images, I have used gimp and I liked it. but if you want to draw diagrams, Google Docs Drawing is a easier option doesnt need anyhting to install
but if you are asking for generating pictures from json, I think we could use dot

for example: someoutput | dot -Tpng -o g output.png

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[afbjorklund]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten