Hi there, if one wanted to temporarily disable the ability for flyte to run new executions (scheduled or manual) via configuration on a deployment, is there a way to accomplish that?

You can pause schedules

As in one at a time or is there a global pause configuration option?

scheduled and manual are pretty different. for scheduled it depends on which scheduler you’re using. previous sample deployments of flyte used sns/sqs. now flyte has its own scheduler pod, which you can disable. if running as a single binary, you can disable through an arg (though I’m not sure this is exposed through the helm configuration so you may need to

inline

it). for manual ones… no not really, short of taking down the server or something. you can hack it by like temporarily removing the CRD or something, which will just cause things to error.

If we are using flyte scheduler pod, when you say we can disable it, do you mean scaling down the deployment to 0?

yeah

Ah gotcha, thanks.