Doesn't Docker port binding obviate the need for Kubernetes' complex networking model? -
kubernetes has pretty complicated networking model appears predicated upon circumventing critical flaw docker's default networking:
by default docker containers cannot contacted directly outside world, because ip addresses local/private subnet they're on.
to circumvent this, kubernetes has complex network model that, amongst other things, requires carve out own flat ip space shared hosts , containers (pods), giving each pod own public ip.
but ask: isn't addressed docker port binding? if not, port binding still lacking, requires kubernetes use networking solution use?
this described in motivation section of kubernetes's networking design doc.
essentially, relying on port binding requires dynamic port mapping avoid conflicts between different containers wanting same port (e.g. lot of applications want port 80). while dynamic port mapping can made work, causes lot of problems, outlined in doc.
Comments
Post a Comment