2 min read
On Kubernetes there are three QoS (Quality of Service) classes that a Pod can use. We can check what's the class it's using by checking the qosClass under status:
$ kubectl get pod pet2cattle-swag-746956854c-62psn -n website -o jsonpath='{.status.qosClass}'
Burstable
10/11/2021
Read more...2 min read
The cluster autoscaler takes into consideration several factors when it chooses a node to remove (evicting it's Pods)
28/10/2021
Read more...3 min read
When we don't have the Pod's resources correctly configured we might face the need of moving a Pod to a different node. Although we could change the nodeSelector or adjust the resources to that it gets scheduled on a different node, it might urge us to fix an issue. To do so we can use kubectl drain
At the end of the day what we want it really is "drain the node of that kind of Pods". As kind of by product the node ends up being cordoned so we are sure the Pod won't be scheduled again on the same node.
25/10/2021
Read more...2 min read
If we need to execute some actions at container startup of before stopping the container we can me use of the container lifecycle hooks
24/09/2021
Read more...2 min read
With a taint on a node we can repel Pods as we saw on the post regarding taints and tolerations. So, if we want to taint a node we use kubectl taint as follows:
$ kubectl taint nodes minikube application=example:NoSchedule
node/minikube tainted
How do we untaint a node?
13/09/2021
Read more...