Summary
The user is asking about the safety of increasing the number of pods in the flyte-binary deployment and whether this requires migrating to flyte-core with separate deployments for components like propeller and datacatalog. It is suggested that using flyte-core is recommended for scaling out, and while adding binary is possible, it may involve changing some configurations that are not well documented, which could lead to issues.
kumare
It’s just splitting up the binary
kumare
It’s non destructive migration
dubovikov.kirill
Ok, understood. We’ll evaluate using core then
kumare
Exactly what I said not documented to scale out
dubovikov.kirill
I meant an example for flyte-binary if there is any
kumare
So please use core
kumare
Wdym, core is documented
dubovikov.kirill
<@UNZB4NW3S> thanks! Is there any example for this?
dubovikov.kirill
Hi Everyone. Could you tell me if it is safe to scale out flyte-binary deployment by increasing the number of pods in the deployment? Or if we want scaling out, we need to migrate to using flyte-core and separate deployments for propeller, datacatalog and etc?
kumare
It is recommended to use core to scale out. You should be able to add binary, the challenge is some config has to be changed but, if it’s not documented well, that might cause trouble