Hi Flyte team, We are planning to upgrade our Flyte components from version 1.11 to 1.15 here at Stripe. As this version upgrade includes several database migrations, particularly for the flyte-admin database, we wanted to ensure we follow the best practices during the rollout. Could you please provide guidance on the recommended approach for this upgrade? Specifically, we would like to know: • Is it acceptable for workflows to continue running while we perform the upgrade? • Should we temporarily disable all registrations and executions during the migration process? Thanks, Ankush ML Infra Software Engineer, Stripe

• Is it acceptable for workflows to continue running while we perform the upgrade?

yes it is, after you restarted your flytepropeller, you will still able to watch the CR's status and do the corresponding action,

• Should we temporarily disable all registrations and executions during the migration process?

during the migration process, every registration will fail if the admin or is restarting, since we will write data to DB via flyteadmin

@damp-lion-88352 Will starting a new execution also fail during migration?

no it will not fail

So what is the recommendation - do we need to pause flyte registrations or is it okay to let flyte run normally during the upgrade migration ?

No just upgrade both together

hey @wonderful-continent-24967 how did the migration go?

hi @average-finland-92144. We rolled out the update in a testing environment, and it went smooth. The only issue is rollback, as the flyte-admin migration drops

admin-tags

&

execution_admin_tags

, but the rollback migration does not recreate these tables, so we have to create these tables manually in case we need to rollback. We plan to rollout the upgrade in production environment in coming weeks.