The configuration in your Tanzu Service Mesh tenant can drift from the desired configuration state defined in the Git repository if someone goes directly to the Tanzu Service Mesh tenant and makes changes. This can cause the Git configuration and the tenant configuration to diverge. You need to implement a mechanism to ensure that the Git repository remains the source of truth for the configuration state.
One option is to create a cron job that runs a script at regular intervals (for example, every 10 minutes). The script will re-apply the manifest files from the Git repository and apply the configurations from the files to Tanzu Service Mesh SaaS at the configured interval. This approach will help overwrite the divergences and automatically drive the configuration state in Git.
Changes made to the configuration in Tanzu Service Mesh SaaS do not affect the manifest files stored in the Git repository. Because Git is the source of truth, the described convergence mechanism will be continuously applying changes from Git to the tenant in SaaS to keep them in sync with the configuration state in the Git repository.
Make sure that the cron job is running on a machine that can access your repository and Tanzu Service Mesh SaaS.
