liveBook · Manning

Network isolation

Network isolation is the restriction or separation of network communication so that systems or processes can communicate only across permitted paths or boundaries.

How 2 Manning books explain it

MongoDB 8.0 in Action, Third Edition

Network isolation is the restriction of communication paths so that protected systems are reachable only through permitted network boundaries.

How it is used
Protects Atlas clusters by limiting connectivity to approved network paths and trusted sources.
How deep it goes
Explains VPC placement, IP access lists, and private endpoints as configuration patterns within defense in depth.
Examples
Uses Atlas clusters in VPCs, restricted IP ranges, and private endpoints as concrete isolation configurations.
What you can do after
Operate/configure Atlas connectivity using VPCs, IP access lists, and private endpoints as layered controls.

Read how MongoDB 8.0 in Action, Third Edition explains network isolation →

Kubernetes in Action, Second Edition

Network isolation is the restriction of network communication so that a pod can communicate only with explicitly permitted pods.

How it is used
Restricts pod-to-pod communication when namespace boundaries alone are insufficient.
How deep it goes
Explains default cross-namespace reachability and NetworkPolicy’s purpose, but stops short of policy syntax and implementation.
Examples
Demonstrates direct pod access from a worker node and a temporary curl client pod.
What you can do after
Evaluate/understand whether namespace boundaries restrict pod connectivity and identify NetworkPolicy as the control mechanism.

Read how Kubernetes in Action, Second Edition explains network isolation →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.