Off the assembly line on elegant application

1 Overview

kubernetes rolling upgrade process:

1.  Cluster Deployment or Statefulset changes, triggering the deployment of a rolling upgrade;
2.  Deolyement other configurations based on, K8S first start a new cluster to replace the old POD POD;
3.  The POD Deployemnt scheduling configuration, pulling the mirror, this time into the POD Pending state;
4.  POD bound to the Node, starting container, it is ready by checking probe readinessProbe new POD enters the Ready state;
5.  K8S cluster creation Endpoint, the new POD included in the load balancing Service;
6.  K8S cluster associated with the removal of the old POD Endpoint, and the old POD status to Terminating, this time there will be no new request arrives old POD, while calling PreStop Hook execution of the script configuration;
7.  K8S old POD cluster will send SIGTERM signal,