IT hands-on

We can deploy " unmanaged " static pods on a specific host, of our choosing, by running the below command on that node: Then we check if the po

We have the below scenario : A single " nginx " pod listening on targePort " 80 ", and a cluster IP service "pointing" to it.

We usually don't build sensitive information like passwords within the application's image. We use a kubernetes object called secret , than we c

We normally don't build sensitive information like password inside the image. In our example, we store them in a kubernetes object called secret , t

Sometimes we get a message, that says that a kubernetes node is not ready, as below: We could also try to describe the node to get more information abo

We have the below  Yaml file of a  pod that is supposed to be scheduled on node " nodeName: worker-1 " : We create that pod using the below comma

Classless Inter-Domain Routing ( CIDR ) is used to extend the IPv4 addressing scheme, using the subnets instead of "wasting" whole IP addresse

To create a deployment of " nginx " pods , we use the below command: To get the status of our deployment , we use the below command: <i><b> Updating the

Following our journey on the  preparation towards the exam CKA (Certified Kubernetes Administrator), we continue this time with exercise number 10. <b> Exe

Resource requests are the "wished" resources that a pod wants to have in regard to - memory and CPU - We could state them through the command

If we have a specific "topology" for our pods that a certain scheduler can handle, we could have a specific deployment Yaml file for our &qu