Goal
Prevent the fusion-config-sync pod from deploying in Fusion 5.9.10+ environment when Git-based configuration synchronization is not required.
Environment
Fusion 5.9.10 and above
Kubernetes-based deployments (e.g., AKS, EKS, GKE)
Helm-managed installation or upgrade
Note: The fusion-config-sync pod is introduced in Fusion 5.9.10 and is not present in earlier versions.
Guide
Understand the purpose of the pod
The fusion-config-sync pod synchronizes configuration data between a Git repository and Fusion. It supports GitOps workflows where application definitions are version-controlled.
If this functionality is not in use, the pod may start and fail due to Git credentials not configured or unsupported SSH key types. In such cases, disabling the pod is a safe and recommended approach. Please refer to this link for more information on config-sync.
Step 1: Locate the fusion_values yaml file
Locate the fusion_values.yaml file used for deploying or upgrading Fusion.
Step 2: Set the enabled flag to false
Add or modify the following block in your fusion_values.yaml file:
fusion-config-sync:
enabled: false
Step 3: Save the configuration
Ensure the modified values file is saved if you are working locally.
Step 4: Apply the configuration via upgrade script
After updating the above block in your fusion_values.yaml file, run the upgrade script :
./gke_..._upgrade_fusion.shUpdate the script as per your environment.
After the upgrade completes, the fusion-config-sync pod should no longer appear in the namespace.
Step 5: Confirm pod removal
Verify the pod is no longer present by running:
kubectl get pods -n <your-namespace> | grep config-syncIf no output is returned, the pod is successfully disabled.