What is the typical prefect version upgrade strategy for a cloud KubernetsAgent?

Hey @Leon Kozlowski, you can delete the old one and the work will queue up if there is no agent to pick it up and then you can start a new process. The flows will continue. If you want a smoother approach, you can use labels to control where the flows go until the old one doesn’t receive anything anymore, and then remove it, but i think this would require re-registration of your flows to the new label, which you might need anyway since the version is upgrading.

I think the queuing should be just fine