Kubernetes does not come with a built-in monitoring services that keeps track of deployments, resource usage, scaling events or Pod crashes. The Kubelet service on Pods has a subcomponent called cAdvisor that monitors node counts, performance and events.…
Its is technically possible to have only one Worker Node in your cluster, with no supporting Master Node to orchestrate scheduling, networking or anything else, for that matter. These singular Pods are called Static Pods.…
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.…
