No, because there is only 1 replica, any changes to state full set would result in an outage.
So rolling update of a StatefulSet would need to tear down one (or more) old pods before replacing them.
In case 2 replicas, a rolling update will create the second pod, which it will not be succeeded, the PD is locked by first (old) running pod, the rolling update is not deleting the first pod in time to release the lock on the PDisk in time for the second pod to use it.
If there's only one that rolling update goes 1 -> 0 -> 1.f the app can run with multiple identical instances concurrently, use a Deployment and roll 1 -> 2 -> 1 instead.
adding to @kalgi's answer
Using just the hostname ...READ MORE
Follow these steps
To create a Kubernetes 1.5 ...READ MORE
Bucket is created in another region. Looks like ...READ MORE
The property concurrencyPolicy is part of the CronJob spec, ...READ MORE
Hey @nmentityvibes, you seem to be using ...READ MORE
Try using ingress itself in this manner
except ...READ MORE
Hi Kalgi after following above steps it ...READ MORE
Follow these steps:
$ kubeadm reset
$ kubeadm init ...READ MORE
Yes, the scheduler will make sure (as ...READ MORE
The Deployment updates Pods in a rolling ...READ MORE