IT hands-on

We start by creating our namespace using the below command:  We can now make our namespace secure by restricting access to it. We could bind a "res

We start by creating pod named " nginx_pod " using an nginx image: To be able to reach our pod from outside the node it "lives" on, w

We have four nginx pods are running on two different nodes. Below is the Yaml file of the deployment of these four nginx replicas that are listening o

For the pods to be able to communicate inside the Kubernetes cluster, they need a CNI - Container Network Interface -.  We will take as an example Cali

Below are the commands that will be used to create the network namespace , the bridge/virtual switch  " br-1 ", veth pairs " veth_0 , veth_1 &

The host network  option works without the need to map the container's port to the host's port. But as we run more and more containers using the

Docker comes with different network drivers that would fit most applications. But if there is a need for a more "customized" network driver,

Looking for files could help us reorganize our system and also remove files that could pose a security risk . Below are some useful " find " com