Hello People,
I’m following the “Docker Certified Associate Exam Course,” and in the fourth module, in the “Docker Engine—Networking” section, there is the “Networking Deep Dive—Namespaces” lesson.
I think that lesson is from another course, and I’m looking for that course.
I don’t have “networking skills”, and I’d like to learn much about them.
Can someone point me to the course with that specific lesson, please?
This unit helps explain how containers “work” in Linux. TLDR? They use what are called “Linux namespaces” to do isolate containers from the hosting Linux operating system. A key part of this is the use of Linux networking namespaces, which give each container their own, isolated view of a networking stack.
So that’s the point of the module. You do need some basic Linux networking concepts to follow this. I don’t think that this material is tested directly except in rather high level architecture related questions. You don’t need deep networking background for this exam to the best of my knowledge.
Thank you for your response, but I’m afraid it doesn’t fully address my original question. While the information about Linux namespaces and their role in container isolation is helpful, I’m specifically looking for the course that contains the “Networking Deep Dive—Namespaces” lesson.
I’m trying to find the exact course that includes this specific lesson, as I believe it might be from a different course than the one I’m currently following.
The same lecture is also used in the CKA course in its prereq section. But in both cases, the underlying networking techniques are not part of that course either. To fully follow this lecture, you need to know a bit about iptables and what commands are used to set up networking on a Linux host. You’d get this in courses like our LFCS course.
@rob_kodekloud is that much detail networking concept required for CKA ? or basic networking concept in linux is fine as I completed linux basic course on this platform
You don’t need to know the details of how network namespaces work for CKA. Simply know that the kubelet sets them up for you and kube-proxy takes care of the routing.