วีดีโอ

I learned a lot from your series even after 3 years. But I have one question when comparing this episode and Step by Step Instructions on Setting up a Multi Node Kubernetes Cluster on CentOS 8 (th-cam.com/video/2Tr7hNW02fg/w-d-xo.html&ab_channel=TheLearningChannel). After executing this line: kubectl scale --replicas=2 deployment/hello-world, why the two pods are running on server 2 in this video, but the 2 pods are running on master and the worker node separately in the video of multi-node kubernetes cluster on centos 8. Thanks

The Best Video, hats off!

When you show interfaces attached to the bridge where is 10.244.1.1?? As in the diagram it should be mentioned, yet it is not. I think it is because bridge creates a local network for pods within the node. To access the internet and pods in other nodes kubernetes services are required.

Some great content is hidden here :) thanks for sharing

what ip address do i put bro

Dude, you're great

What to do if I'm setting up a malware testing lab

Really Great Work. So grateful I watched this on. Cleared everything for me. All my confusion and doubt's are gone related to networking. Thank you so much 🙏 I would recommend my peers to watch this.

1 question here. You setup both bridges in ubuntu1 and ubuntu2 to have different ips here. But since the bridges are in different vms they could have had same ip. In that case when we ping from namespace1 how will it be able to reach namespace2's bridge ?

exellent!

This video helped me 1000%. Explanation is very clear, Thank you.

@TheLearningChannel-Tech Could you please clarify why the inner IP header contains the tunnel IP address (172.23.94.0) instead of the pod IP address (172.23.94.6)? For the response packet from the pod (172.23.61.206), it correctly uses the pod IP as the source IP (172.23.61.206, response packet doesn't have source ip as tun ip), which seems to align with Kubernetes documentation suggesting that pod-to-pod communication should avoid NAT. Ideally, it seems that the inner IP should reflect 172.23.94.6 as the source and 172.23.61.206 as the destination. Thank you for posting such an amazing video and creating great content on Kubernetes networking.

At 38:16, note that in Ubuntu 22.04.5 LTS, the "via" option is not available. Instead execute the command as `sudo ip route add $TO_BRIDGE_SUBNET $TO_NODE_IP dev eth0`

i am impressed by how concise and pretty your graphics are

Excellent video, excellent demo, excellent way to present the whole video. Appreciate your time and efforts for creating this series. This video is unmatachable. Amazing work sir. ❤👏👏👏

im cka certified. it is good to have kubernetes networking knowledge that they didnt go deep into. Very good and comprehensive content

My man has answers to satisfy my ADHD itch to understand something at this level of depth.

I can not ping server2 containers from server1 containers. root@ip-192-168-1-141:~# sudo ip netns exec ns1 ping -W 1 -c 2 172.16.0.1 PING 172.16.0.1 (172.16.0.1) 56(84) bytes of data. --- 172.16.0.1 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1011ms root@ip-192-168-1-141:~# ip netns exec ns1 route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 172.16.1.1 0.0.0.0 UG 0 0 0 veth11 172.16.1.0 0.0.0.0 255.255.255.0 U 0 0 0 veth11 192.168.1.0 172.16.1.1 255.255.255.0 UG 0 0 0 veth11

Thank you for sharing such a detailed study for Kubernetes Networking. Great work!

when the vms are on different subnet, can we not add a route on the router to establish routing?

Awesome video👏. Concepts Very well explained. Thanks!

38:32

I have learnt a lot from your channel. Keep generating such amazing content. It would be great, if there are more frequent videos.

hi thanks for this helpful video I have a question : How does work default route in pod and which interface this ip dedicated set up ? where send all packets this default gateway after receive packets from pod that connect throughout veth interface to the bridge ?? Could you answer my question please ?

Great content, Thank!

@TheLearningChannel-Tech : Thanks for your wonderful session, But I tried on my Virtual box VM's, I'm unable to ping from NS1 to NS2 itself using bridge.. Would you please help me here?

@The Learning Channel: Thanks a lot this video, it’s have very good explanation. My question: Is this applicable for VirtualBox VM’s ? Or only for Hyper-V? In my virtual box VM I see network adapter selected as NAT Adapter, Do you have any procedure for that? Greatly Appreciated!!

Finally Video with No quirky jokes instead just pure knowledge . Thank you

Whenever I face any issues with k8s networking, I come to your channel. Precise, concise and brilliant content!!!

one of the best Azure related contents. all important aspects are mentioned perfectly

can you continue kubernetes to advanced level it would be a great help

guys i think we found Jesus

perfect as always

Thanks for the detailed explanation.

perfect content

perfect demonstration

Hi Can you assit i have configured the cluster but pods from linux worker cant reach pods on Windows worker

Excellent video. Great explanation. This is the video I was looking for.

Great content! Do you have any Udemy channel or other learning platforms?

Very nice videos sir, thank you for the content! I have a question, when we will renew kubernetes certificates, do we need to reconnect the clusters?

Thanks

most videos/blogs teach on how to install in ubuntu os. you're the first one i've seen to teach how to install on fedora like system. thank you so much

Hi, I like your video, it´s informative. I tried a lot today to implement this scenario but unfortunately i could not. I can ping in ubuntu1 machine but i cannot ping from one to another. i am describing what i did so you can understand my problem, i have created two vm machine in virtual box and i created same script in 2 machines but i have changed the ip address of ubuntu2 to 172.168.1.0. my question is, i have seen you run the command in one machine and you still can communicate both, did you skip ubuntu2 machine configuration?

This is the best video that explains the virtual networking concept

hi i followed the steps. everything is working. pod connectivity. service. clusterip. nodeport. but i cannot reach kube-dns from within a pod. do you happen to know what might be the cause?

hi. how do you higlight the line and run in the terminal in vscode?

I must say that this playlist is the best on Kubernetes networking, starting with the lowest layer till the highest layer.

Your videos are really great and very helpful, could not find any better than this on youtube to understand kubernetes networking in depth. can you please create some videos on kubernetes troubleshooting as well?

Thank you very much for sharing. It is really good all explanation in all series.

33:35 isnt this wrong that the response is SNAT'ed? Because traffic has already been DNAT'et, the local node will know of the connection in its conntrack table, and it does not need to SNAT... ?