In this multi-part exercise, you will use System Sync to test two-way synchronization between the system and a Git repository for EKS clusters. You will create an EKS cluster from your Git repository and update the cluster from both the system and Git to see the changes applied and synchronized.
System Sync enables two-way or bidirectional synchronization to maintain the configuration in the system (system database) and Git repository. Any configuration changes performed in the Git repository get reflected in the system, and vice-versa is supported. To achieve this bidirectional sync, external and internal triggers are required. External triggers (Pipeline Triggers) notify whenever resources are modified in a Git repository, and internal triggers notify whenever resources are modified in an internal artifact store.
What Will You Do¶
|Part||What will you do?|
|1||In this part, you will Configure and Setup an Environment in order to test System Sync with EKS clusters|
|2||In this part, you will use System Sync to Create an EKS Cluster from Git|
|3||In this part, you will use System Sync to Update an EKS Cluster from the system|
This exercise assumes that you have access to the following:
- An Org with Org Admin privileges
- A provisioned or imported cluster
- An AWS Cloud Credential
- An account on GitHub for GitOps operations