Learn KOP - Part 2 - Sync Blueprint - Rafay Product Documentation

Part 2: Sync Blueprint

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


What Will You Do

In part 2, you will test bidirectional syncing of a blueprint. You will synchronize the custom blueprint from the system to your Git repository. You will then update the spec file in the Git repository and have it applied on the system.


Step 1: Initial Sync

First, we will manually run the pipeline in order to sync the system resources to the GitHub repository.

We can see that the blueprint and workload manifest have been created in the Git repository


Step 2: Update Blueprint From Git

In this step, we will update the blueprint version in the Git repository and then witness the updates applied automatically in the system.

The update will trigger the GitOps pipeline and it will automatically update the blueprint. We can see that the blueprint now has two versions associated with it.

Navigate to GitOps -> Pipelines in the console to see that a second job in the pipeline was initiated. This job was triggered via a GitHub webhook when we committed the YAML file update.


Step 3: Update Blueprint From System

In this step, we will update the blueprint version from the system and then witness the update being applied automatically in the Git repository.

The update will trigger the GitOps pipeline and it will automatically update the blueprint spec file in the Git repository.


Recap

In this part, you tested two-way, bidirectional synchronization between the system and your Git repository for blueprints.