GitOps Application Lifecycle - Rafay Product Documentation

Part 3: Pipeline

What Will You Do

In this section you will


Step 1: Create Pipeline

The GitOps pipeline will be used to deploy/update workloads from the Git repository each time an update is made and committed to the repo.


Step 2: Add Pipeline Stages

A pipeline can have multiple stages, with completely different actions to model your desired workflows. In this exercise, you will create a three stage pipeline that will first seek user approval, then deploy/update the YAML workload and finally deploy/update the Helm workload.

Next, you will add a pipeline stage that will deploy/update the YAML workload.

Next, you will add a pipeline stage that will deploy/update the Helm workload.


Step 3: Add Pipeline Trigger

A pipeline can be executed based on an "external trigger". For example, changes to the manifests in your Git repository. In this exercise, you will configure a trigger that will receive a webhook notification when specific files and directories in your Git repository are modified.

You will now be presented with the webhook configuration details that you need to copy/paste to your GitHub repository. Once you complete this step, the GitOps pipeline will be configured to receive webhook notifications whenever the repository is updated in Git.


Step 4: Setup GitHub Webhook

In this step, we will configure the GitHub repository to send a webhook to the controller when updates are made to the repo.


Step 5: Activate Pipeline

By default, newly created pipelines start life in a deactivated state. You will activate the pipeline in this step so that it can be used.


Recap

At this point, you have successfully setup a multistage GitOps pipeline that is triggered by commits to a Github repository.