IT hands-on

After its installation,  kubernetes creates a bunch of default roles . These roles are what define the "rights" of a  kubernetes account  in the

Usually pods are not scheduled on the master node , but if for whatever reason we need to do it, we would start by looking for the taints of the master

We start by checking our pods : The above pods are deployed using a deployment object. We could look for their  deployment object  using the below command:

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

In our example we have a deployment with three replicas of the " nginx " pod . Below is the Yaml file of our deployment : We create our deployment

We can assign priorities to pods , and as a result a pod with a lower priority might be stopped to allow a higher priority pod to be scheduled if the re

A hostPath Volume  mounts a directory on the pod's filesystem so that its containers can have access to a storage space. Below is a Yaml file of a p