Skip to content

Part 3: Sync from System

This is Part 3 of a multi-part, self-paced quick start exercise.


What Will You Do

In part 3, you will test syncronization to the Git repository. You will make changes to the EKS cluster from the console and witness the changes applied in your Git repository automatically.


Step 1: Update Cluster from System

In this step, we will add a nodegroup to the EKS Cluster from the console and witness the update applied automatically in the Git repository.

  • Navigate to Infratructure -> Clusters
  • Click on your Cluster
  • Navigate to the "Node Group" tab
  • Click "Add Node Group"
  • Provide a name for hte node group
  • Click "Provision Node Group"

After the node group has been created, the GitOps pipeline will run and syncronize the change with the Git repository. We can see that the second node group was added to the cluster spec file in Git.

System Update


Step 2: Delete Cluster from System

In this step, we will delete the EKS cluster from the system console and see that the cluster spec file is removed from the Git repository. A cluster, unlike other infrastructure resources, cannot be deleted by removing the spec file from the Git repository. The deletion of a cluster must be initiated from the system.

  • Navigate to Infratructure -> Clusters
  • Click on the gear icon of your Cluster
  • Click "Delete"

The deletion will trigger the Gitops pipeline and it will automatically remove the cluster spec from the Git repository.

System Delete


Recap

In this guide, we tested portions of EKS cluster lifecycle management using a GitOps pipeline with System Sync. We witnessed the bidirectional syncronization between the system and a Git repository showing that changes can be made in either location and will be reflected on the other.