IP Address Exhaustion solve using NAT in k3s cluster? How it works? Good materia

Started by networkloser, June 01, 2025, 11:36:56 PM

Previous topic - Next topic

networkloser

l to learn these topics? I mean I just want to learn this exact chapter from a book, what topics should I seek? I am trying to implement it on k3s.


deanwebb

NAT is a tricky thing, though. Used one time with the Internet connection, it is manageable. If it is used a second time for masking internal traffic, then problems develop. Problems multiply if address spaces are re-used in different areas and NAT is employed to mask the IP address re-use. This last scenario is common in industrial environments.

In the K3S cluster, how many nodes are being used? If the number is over 64K, then we may want to instead go with IPv6 instead of IPv4 with NAT.
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.