Unable to update redis/minio in cluster
During the demo today, on Kubernetes 1.9.7-gke.3
we noticed that minio and redis could not bring up new pods, because the old pods were still holding the mounts.
From looking at the deployment yaml, this appeared to us to be because the update strategy was set to rolling, with a maxUnavailable: 25%
which we have not set ourselves in the charts.
In order to move forward, we had to issue a scale=0 to the old replicaset for redis and minio. Then the new pods were able to attach the volumes and start.
Edited by DJ Mountney