I finally wrote a piece of software I've wanted for years - a bot that regularly monitors the stock market for good, fundamentally sound companies that are undervalued, and then lets me know as soon as it finds them.…
Kube-scheduler, if you recall, is a service that runs on the master node that monitors the cluster for unscheduled pods. It does this by checking for a property called nodeName on a created Pods definition.…
ReplicationSets and/or Replication Controllers are processes that ensure that a certain number of identical pods are always running on your cluster. If a pod fails the ReplicationSet or Replication Controller will remove it and replace it with a new one.…
As mentioned in the first Kubernetes post in this series, the Worker nodes have two Kubernetes Cluster Control Plane processes running on them that help them stay coordinated with the Master node and cluster as a whole; Kubelet and Kube-proxy.…
The Master node is usually a single node in your cluster that orchestrates the whole shebang. It consists of 3 processes - the Kube-Api-Server, the Kube-Control-Manager and the Kube-scheduler.…
The speed and ease the deployment that containers quickly resulted in the need for a way to manage state between different containers, to scale deployments dynamically and remove and replace containers that started acting up.…
