Kubernetes also maintains a history (the length of which can also be controlled) for rollouts. You can see the state of a rollout, as well as its history, through the kubectl rollout command.
For example, to see the status of the rollout that we just did:
kubectl rollout status deployment/flask
deployment "flask" successfully rolled out
And you can view the history of the changes to the deployment with the following:
kubectl rollout history deployment/flask
deployments "flask"REVISION CHANGE-CAUSE1 <none>2 <none>
change-cause is tracked as an annotation on the deployment resource, which (as of Kubernetes 1.8) does not exist, since we created the deployment with the default kubectl run command. There is a --record=true option, ...
