This guide presents a basic introduction to Harness GitOps PR Pipelines. Together, we will:

1. Create a local Kubernetes cluster.

2. Install GitOps Agent.

3. Demonstrate how we can progress changes through multiple environments by interacting with your GitOps repository and ApplicationSet.

4. Clean up.

• Docker
• kind or k3d: These instructions were tested with:
  • kind: v0.19.0
  • k3d: v5.4.9

kind create cluster \
  --wait 120s \
  --config - <<EOF
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
name: pr-quickstart
EOF

k3d cluster create pr-quickstart \
  --no-lb \
  --k3s-arg '--disable=traefik@server:0' \
  --wait

1. In GitOps, click Settings, and then Clusters.

   

2. Click New Cluster.

3. In Name, enter the name appset-example.

4. In GitOps Agent, select the Agent you installed earlier.

5. Click Continue.

6. In Details, click Use the credentials of a specific Harness GitOps Agent.

7. Click Save and Continue. The connections is verified.

   

8. Click Finish.

We'll add Harness GitOps Clusters for the two target clusters where we want to add our application.

1. Create a new Harness GitOps Cluster for your dev cluster.

2. Name the cluster dev.

3. In GitOps Agent, select the GitOps Agent you added earlier.

   

4. In Details, select Specify Kubernetes Cluster URL and credentials.

5. In Master URL, enter the Endpoint URL for the target cluster (you can use kubectl cluster-info or your cloud console). Ensure that you use the https:// scheme. Here's an example:

   

6. In Authentication, use the authentication method you prefer. In this tutorial, we use the se-name namespace service-account token.

7. Click Save and Continue. The GitOps Cluster is verified.

8. Click Finish.

You might see a Warning status. This status simply indicates that nothing has been deployed to the cluster yet.

In this step, we will create a GitOps repo on GitHub to house variations of our application manifests for different environments: dev, stage, and prod.

Visit https://github.com/mansong1/pr-demo and fork the repository into your own GitHub account.

You can explore the repository and see that the main branch contains common configuration in a base/ directory as well as environment-specific overlays in paths of the form env/<environment name>/. Kustomize is used as a configuration management tool that combines base configuration with environment-specific configuration.

:::note This layout is typical of a GitOps repository using Kustomize and is not at all Harness specific. :::

To clean up, we will simply destroy our kind or k3d cluster:

kind delete cluster --name pr-quickstart

k3d cluster delete pr-quickstart