In this post we'll have a look at how to keep the actual infrastructure your application is running on up to date and secure, without interrupting service. We'll also have a brief look at disaster recovery, and what to do when things eventually go catastrophically wrong.…
This post covers general deployments tasks like, rollouts, rollbacks, environment variables, multi-container pods and browsing pods.…
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.…
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.…
Namespaces is a way for you to isolate objects, resources and instances in your cluster in a way that they can't interfere with each other.…
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.…
