• Keeping record of the change cause using the --record flag

    3 min read

    kubectl rolling update history change-cause

    On Kubernetes, when we update objects such as a deployment or a daemonset we can check it's rollout history using kubectl rollout history:

    $ kubectl rollout history deploy pet2cattle
deployment.apps/pet2cattle 
REVISION  CHANGE-CAUSE
21        <none>
22        <none>
23        <none>
24        <none>
26        <none>
28        <none>
29        <none>
30        <none>
32        <none>
33        <none>
34        <none>

    By default we won't be able to see a change cause, but we can fill this gap by setting the command that triggered the update adding the --record flag as follows:

    $ kubectl scale deployment/pet2cattle --replicas 2 --record
deployment.apps/pet2cattle scaled

    18/05/2021

    Read more...

From pet to cattle
Treat your kubernetes clusters like cattle, not pets