Rolling deployment restart doesn't restart the pod

[masayag]

Rolling deployment restart doesn't restart the pod

[gazarenkov]

Good point, @rm3l !
Yes, I think it come with the fact that version 1.1 (0.1) watches Deployment.
Just tested oc rollout restart deployment with next version and it works fine.

[gazarenkov]

Hi @masayag

Thanks for the feedback!
I can confirm that oc rollout restart deployment does not work as expected, it does not recreate the pod and so if you change associated ConfigMap or Secret it is not refreshed. This needs some further investigation, so if you find some additional info please share.
Meantime, if you need to apply the changes in CM/Secrets (until we implement #236) one of the following can be used:

• delete the pod and let replicaSet to recreate it. The simplest for single replica IMO
• scale to 0 and then back Backstage CR using Spec's replicas field

[rm3l]

IIRC, kubectl rollout restart would add the kubectl.kubernetes.io/restartedAt annotation, which causes the Pod to restart, but (my guess) is that the Operator would overwrite these annotations.
As an additional workaround, I usually delete the Deployment, and the Operator would recreate it. But this workaround (same with #281 (comment) above) would unfortunately cause some downtime, I guess.

[gazarenkov]

Works on 1.2.
Closing this issue, please feel free to reopen if needed