Summary
The user is experiencing issues after updating their Flyte deployment from version 1.9 to 1.12 in AWS, specifically with 24/7 clusters. They have a control plane in one AWS account and multiple data planes in other accounts, each with its own IAM roles for service accounts. The user is confused about why the control plane's service account-namespace mapping seems to overwrite the data planes' mappings, leading to incorrect IAM roles being assigned to the default service accounts. This results in errors when scheduled workflows attempt to assume the wrong role. The user is seeking guidance on how to adjust this behavior, particularly regarding the syncresources function and whether certain configurations in the control plane should be omitted.