/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 lwn.net
Namespaces in operation, part 7: Network namespaces [LWN.net]
| | blog.quarkslab.com
Digging into Linux namespaces - part 1
1.4 parsecs away

Travel
| | [AI summary] The provided text discusses the use of Linux namespaces to isolate network stacks, enabling the creation of isolated environments for processes. It covers topics such as network namespaces, virtual interfaces, bridges, and iptables rules to enable communication between namespaces and the outside world. The text also touches on other namespaces like USER, MNT, UTS, IPC, and CGROUP, and references various resources for further reading.
| | blog.yadutaf.fr
Introduction to Linux namespaces - Part 5: NET | Yet another enthusiast blog!
1.5 parsecs away

Travel
| | [AI summary] This tutorial explains how to isolate and manage network interfaces using Linux NET namespaces, demonstrating practical implementation with veth pairs and a C program.
| | zserge.com
Linux containers in a few lines of code
2.2 parsecs away

Travel
| | Trying to figure out how Linux containers work by implementing them from scratch in C.
| | blog.nuculabs.de
Kubernetes service account for pod | NucuLabs
22.0 parsecs away

Travel
| Hi ?, In this article I will talk about how to authenticate your applications to the Kubernetes API via the service accounts feature. Citing the Kubernetes docs, a service account for a pod: "provides an identity for processes that run in a Pod. When you (a human) access the cluster (for example, using kubectl), you are authenticated by the apiserver as a particular User Account (currently this is usually admin, unless your cluster administrator has customized your cluster). Processes in containers inside pods can also contact the apiserver. When they do, they are authenticated as a particular Service Account (for example, default)."