Is the rolling update of pod similar to Canary deployment or blue-green deployment?

Canary deployment （ Gray scale deployment ）： Give priority to releasing one or a few machine upgrades , Update other machines after verification . The advantage is that the influence range of users is small , The disadvantage is to control how to update automatically .

Blue and green deployment ：2 Group machine , Blue represents the current V1 edition , Green represents the upgraded V2 edition . adopt LB Import all traffic V2 Complete the upgrade deployment . The advantage is fast switching , The disadvantage is that it affects all users .

Scroll to update ： Multiple running in a cluster Pod edition , The process of upgrading alternately one by one , Namely “ Scroll to update ”, The benefits are obvious . such as , At the beginning of the upgrade , There are only 1 A new version of Pod, If this is the new version Pod There's a problem and it won't start , that “ Scroll to update ” Will stop , This allows developers and O & M personnel to intervene . And in the process , Because the application itself has two old versions Pod On-line , So the service will not be greatly affected .

Conclusion ：pod The rolling update of is an automated Canary release .