Le lun. 3 févr. 2020 à 19:28, Daniel Walsh <dwalsh@redhat.com> a écrit :

On 2/1/20 3:28 AM, laurent.pellegrino@gmail.com wrote:
> Hi there!
>
> I discovered Podman recently and started to use it as a great alternative to Docker.
>
> My question is about application updates. Let's say you have a pod running and you want to update the code for the app in that pod. Is there a simple manner to manage something similar to a Kubernetes rolling update? By rolling update, I mean performing an update with no service interruptions (i.e. starting a new pod running the new app version, switch the network traffic to the new pod and terminate the old pod).
>
> Kind Regards,
>
> Laurent Pellegrino
> _______________________________________________
> Podman mailing list -- podman@lists.podman.io
> To unsubscribe send an email to podman-leave@lists.podman.io

We are actually investigating this workflow. But have not taken as far
as you want. The idea would be to be running a container, and then have
a job start periodically that would see if their was an update to the
image that the container was running on. It would pull the image down
and restart the container service, which would destroy the old container
and create a new container with the same params. This however would not
maintain the the connections.
_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io