import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

This tutorial will get you started with Harness Continuous Delivery (CD). We will guide you through deploying new Cloud Functions to Google Cloud using Harness CD pipeline.

:::info

Sign up today to unleash the potential of intelligent Harness CD.

:::

Harness CD pipelines allow you to orchestrate and automate your deployment workflows, and push updated application images to your target Kubernetes cluster. Pipelines allow extensive control over how you want to progress artifacts through various dev / test / stage / prod clusters, while running a variety of scans & tests to ensure quality and stability standards you and team may have defined.

Verify that you have the following:

1. Obtain GitHub personal access token with the repo scope. See the GitHub documentation on creating a personal access token.
2. A Kubernetes cluster. Use your own Kubernetes cluster or we recommend using K3D for installing Harness Delegates and deploying a sample application in a local development environment.
   • Check Delegate system requirements.
3. Install the Docker in order to install the Docker delegate.
4. Fork the harnessed-example-apps repository through the GitHub website.
   • For details on Forking a GitHub repository, go to GitHub docs for more information on forking a GitHub repository.
5. ** Google Cloud Function and Google Cloud Storage Permission**. Harness supports Google Cloud Functions 1st and 2nd gen. There are minor differences in the permissions required by each generation. For a detailed breakdown, go to Access control with IAM from Google.

Cloud Functions offers two product versions: Cloud Functions (1st gen), the original version, and Cloud Functions (2nd gen), a new version built on Cloud Run and Eventarc to provide an enhanced feature set. Harness supports deploying Google Functions 1st gen and 2nd gen.

To get more information on Google Function 1st gen and 2nd gen, refer Cloud Functions version comparison.

We suggest opting for Cloud Functions (2nd gen) whenever feasible for new functions, as it offers a range of additional features. You can refer New in Cloud Functions(2nd Gen) doc for more information.

• For Google Cloud Functions 2nd gen, Harness does not support Google Cloud Source Repository at this time. Only Google Cloud Storage is supported.
• For Google Cloud Functions 1st gen, Harness supports both Google Cloud Storage and Google Cloud Source.

• Make sure you have appropriate permission on the Google Cloud Function and Google Cloud Storage as mentioned above.
• Download the hello_world.zip for 1st gen and helloHttp.zip for 2nd gen files from GitHub.
• Login to Google Cloud console and create a Bucket, Refer Create a new bucket doc from Google Cloud.
• Once the bucket is created, Click on the UPLOAD FILES and upload hello_world.zip and helloHttp.zip files.

<Tabs>
<TabItem value="2nd Gen">

1. Login to Harness.

2. Select Projects, and then select Default Project

:::caution

For the pipeline to run successfully, please follow the remaining steps as they are, including the naming conventions.

:::

3. Under Project Setup, select Delegates.

   • Select Delegates.

     • Select New Delegate.

     • Click on Docker

       For this tutorial, let's explore how to install a delegate using Docker.

     • In the command provided, ACCOUNT_ID and MANAGER_ENDPOINT are auto-populated values that you can obtain from the delegate installation wizard.

     • Replace DELEGATE_TOKEN in the command with the token that was copied earlier and proceed with delegate installation.

     docker run -dit --cpus=1 --memory=2g \
      -e DELEGATE_NAME=docker-delegate \
      -e NEXT_GEN="true" \
      -e DELEGATE_TYPE="DOCKER" \
      -e ACCOUNT_ID=ACCOUNT_ID \
      -e DELEGATE_TOKEN=DELEGATE_TOKEN \
      -e LOG_STREAMING_SERVICE_URL=https://app.harness.io/gratis/log-service/ \
      -e MANAGER_HOST_AND_PORT=https://app.harness.io/gratis harness/delegate:23.05.79310

     • Select Verify to verify that the delegate is installed successfully and can connect to the Harness Manager.

:::note

You can also follow the Install Harness Delegate on Kubernetes or Docker tutorial to install the delegate using the Harness Terraform Provider or a Kubernetes manifest.

:::

4. Under Project Setup, select Secrets.

   • Select New Secret, and then select Text.
   • Enter the secret name harness_gitpat.
   • For the secret value, paste the GitHub personal access token you saved earlier.
   • Select Save.

5. Under Project Setup, select Secrets.

   • Select New Secret, and then select File.
   • Enter the secret name gcp.
   • For the secret value, Upload the credentials for your service account which you can download from gcp project.
   • Select Save.

5. Create the GitHub connector.

   • Copy the contents of 1-github-connector.yml
   • In your Harness project in the Harness Manager, under Project Setup, select Connectors.
   • Select Create via YAML Builder and paste the copied YAML.
   • Assuming you have already forked the harnessed-example-apps repository mentioned earlier, replace GITHUB_USERNAME with your GitHub account username in the YAML.
   • In projectIdentifier, verify that the project identifier is correct. You can see the Id in the browser URL (after account). If it is incorrect, the Harness YAML editor will suggest the correct Id.
   • Select Save Changes and verify that the new connector named harness_gitconnector is successfully created.
   • Finally, select Connection Test under Connectivity Status to ensure the connection is successful.

6. Create the GCP connector.

   • Copy the contents of 2-gcp-connector.yml.
   • In your Harness project, under Project Setup, select Connectors.
   • Select Create via YAML Builder and and paste the copied YAML.
   • Select Save Changes and verify that the new connector named gcpconnector is successfully created.
   • Finally, select Connection Test under Connectivity Status to verify the connection is successful.

7. In your Harness project, select Environments.
   • Select New Environment, and then select YAML.
   • Copy the contents of 3-environment.yml, paste it into the YAML editor, and select Save.
   • In your new environment, select the Infrastructure Definitions tab.
   • Select Infrastructure Definition, and then select YAML.
   • Copy the contents of 4-infrastructure-definition.yml and paste it into the YAML editor.
   • Replace GCP PROJECT NAME with your gcp project name.
   • Replace GCP REGION with your gcp region name.
   • Select Save and verify that the environment and infrastructure definition are created successfully.

8. In your Harness project, select Services.
   • Select New Service.
   • Enter the name hello_http.
   • Select Save, and then YAML (on the Configuration tab).
   • Select Edit YAML, copy the contents of 5-service-gen2.yml, and paste the into the YAML editor.
   • Replace GCP PROJECT with your gcp project name.
   • Replace GCP BUCKET with your gcp bucket name.
   • Select Save, and verify that the service hello_http is successfully created.

9. In your Harness project, select Pipelines.

• Select Create a Pipeline.
• Enter the name hello_http.
• Select Inline to store the pipeline in Harness.
• Select Start.
• In Pipeline Studio, select YAML.
• Select Edit YAML and choose any of the following execution strategies. Paste the respective YAML based on your selection.

<Tabs>
<TabItem value="Canary">

• Copy the contents of 6-canary-deployment-gen2.yml.

• In your Harness pipeline YAML editor, paste the YAML.

• Select Save.

  You can switch to the Visual editor and confirm the pipeline stage and execution steps as shown below.

<docimage path={require('../static/harness-cicd-tutorial/canary-gen2.png')} width="60%" height="60%" title="Click to view full size image" />

</TabItem>
<TabItem value="Blue Green">

• Copy the contents of 6-bluegreen-deployment-gen2.yml.

• In your Harness pipeline YAML editor, paste the YAML.

• Select Save.

  You can switch to the Visual pipeline editor and confirm the pipeline stage and execution steps as shown below.

<docimage path={require('../static/harness-cicd-tutorial/bluegreen-gen2.png')} width="60%" height="60%" title="Click to view full size image" />

</TabItem>
<TabItem value="Rolling">

• Copy the contents of 6-rolling-deployment-gen2.yml.

• In your Harness pipeline YAML editor, paste the YAML.

• Select Save.

  You can switch to the Visual pipeline editor and confirm the pipeline stage and execution steps as shown below.

<docimage path={require('../static/harness-cicd-tutorial/rolling-gen2.png')} width="60%" height="60%" title="Click to view full size image" />

</TabItem>
</Tabs>

Finally, it's time to execute your pipeline.

10. Select Run, and then select Run Pipeline to initiate the deployment.

• Observe the execution logs as Harness deploys the workload and checks for steady state.
• After a successful execution, you can check the deployment on your Google Cloud Function console.

You've just learned how to use Harness CD to deploy an application using a Google Cloud Functions gen 2 to Google Cloud.

• Keep learning about Harness CD. For example, add Triggers to your pipeline that initiate pipeline deployments in response to Git events.
• Visit the Harness Developer Hub for more tutorials and resources.

</TabItem>
<TabItem value="1st Gen">

1. Login to Harness.

2. Select Projects, and then select Default Project

:::caution

For the pipeline to run successfully, please follow the remaining steps as they are, including the naming conventions.

:::

3. Under Project Setup, select Delegates.

   • Select Delegates.

     • Select New Delegate.

       For this tutorial, let's explore how to install a delegate using Helm.

     • Add the Harness Helm chart repo to your local helm registry using the following commands.

     helm repo add harness-delegate https://app.harness.io/storage/harness-download/delegate-helm-chart/

     • Update the repo:

     helm repo update harness-delegate

     • In the command provided, ACCOUNT_ID and MANAGER_ENDPOINT are auto-populated values that you can obtain from the delegate installation wizard.
     • Replace DELEGATE_TOKEN in the command with the token that was copied earlier and proceed with delegate installation.

     helm upgrade -i helm-delegate --namespace harness-delegate-ng --create-namespace \
     harness-delegate/harness-delegate-ng \
      --set delegateName=helm-delegate \
      --set accountId=ACCOUNT_ID \
      --set managerEndpoint=MANAGER_ENDPOINT \
      --set delegateDockerImage=harness/delegate:23.03.78904 \
      --set replicas=1 --set upgrader.enabled=false \
      --set delegateToken=DELEGATE_TOKEN

     • Select Verify to verify that the delegate is installed successfully and can connect to the Harness Manager.

:::note

You can also follow the Install Harness Delegate on Kubernetes or Docker tutorial to install the delegate using the Harness Terraform Provider or a Kubernetes manifest.

:::

4. Under Project Setup, select Secrets.
   • Select New Secret, and then select Text.
   • Enter the secret name harness_gitpat.
   • For the secret value, paste the GitHub personal access token you saved earlier.
   • Select Save.

5. Create the GitHub connector.

   • Copy the contents of 1-github-connector.yml
   • In your Harness project in the Harness Manager, under Project Setup, select Connectors.
   • Select Create via YAML Builder and paste the copied YAML.
   • Assuming you have already forked the harnessed-example-apps repository mentioned earlier, replace GITHUB_USERNAME with your GitHub account username in the YAML.
   • In projectIdentifier, verify that the project identifier is correct. You can see the Id in the browser URL (after account). If it is incorrect, the Harness YAML editor will suggest the correct Id.
   • Select Save Changes and verify that the new connector named harness_gitconnector is successfully created.
   • Finally, select Connection Test under Connectivity Status to ensure the connection is successful.

6. Create the Kubernetes connector.

   • Copy the contents of 2-kubernetes-connector.yml.
   • In your Harness project, under Project Setup, select Connectors.
   • Select Create via YAML Builder and and paste the copied YAML.
   • Replace DELEGATE_NAME with the installed Delegate name. To obtain the Delegate name, navigate to Project Setup, and then Delegates.
   • Select Save Changes and verify that the new connector named harness_k8sconnector is successfully created.
   • Finally, select Connection Test under Connectivity Status to verify the connection is successful.

7. In your Harness project, select Environments.
   • Select New Environment, and then select YAML.
   • Copy the contents of 3-environment.yml, paste it into the YAML editor, and select Save.
   • In your new environment, select the Infrastructure Definitions tab.
   • Select Infrastructure Definition, and then select YAML.
   • Copy the contents of 4-infrastructure-definition.yml and paste it into the YAML editor.
   • Select Save and verify that the environment and infrastructure definition are created successfully.

8. In your Harness project, select Services.
   • Select New Service.
   • Enter the name hello_world.
   • Select Save, and then YAML (on the Configuration tab).
   • Select Edit YAML, copy the contents of 7-service-gen1.yml , and paste the into the YAML editor.
   • Replace project with your gcp project name.
   • Replace bucket with your gcp bucket name.
   • Replace artifactPath with the hello_world.zip file path from google bucket
   • Select Save, and verify that the service hello_world is successfully created.

9. In your Harness project, select Pipelines.

• Select Create a Pipeline.
• Enter the name hello_world.
• Select Inline to store the pipeline in Harness.
• Select Start.
• In Pipeline Studio, select YAML.
• Select Edit YAML and choose any of the following execution strategies. Paste the respective YAML based on your selection.

<Tabs>
<TabItem value="Canary">

• Copy the contents of 7-canary-deployment-gen1.yml.

• In your Harness pipeline YAML editor, paste the YAML.

• Select Save.

  You can switch to the Visual editor and confirm the pipeline stage and execution steps as shown below.

<docimage path={require('../static/harness-cicd-tutorial/canary-gen2.png')} width="60%" height="60%" title="Click to view full size image" />

</TabItem>
<TabItem value="Blue Green">

• Copy the contents of 7-bluegreen-deployment-gen1.yml.

• In your Harness pipeline YAML editor, paste the YAML.

• Select Save.

  You can switch to the Visual pipeline editor and confirm the pipeline stage and execution steps as shown below.

<docimage path={require('../static/harness-cicd-tutorial/canary-gen2.png')} width="60%" height="60%" title="Click to view full size image" />

</TabItem>
<TabItem value="Rolling">

• Copy the contents of 7-rolling-deployment-gen1.yml.

• In your Harness pipeline YAML editor, paste the YAML.

• Select Save.

  You can switch to the Visual pipeline editor and confirm the pipeline stage and execution steps as shown below.

<docimage path={require('../static/harness-cicd-tutorial/canary-gen2.png')} width="60%" height="60%" title="Click to view full size image" />

</TabItem>
</Tabs>

Finally, it's time to execute your pipeline.

10. Select Run, and then select Run Pipeline to initiate the deployment.

• Observe the execution logs as Harness deploys the workload and checks for steady state.
• After a successful execution, you can check the deployment on your Google Cloud Function console.

You've just learned how to use Harness CD to deploy an application using a Google Cloud Functions gen 1 to Google Cloud.

• Keep learning about Harness GitOps. Create a GitOps ApplicationSet and PR Pipeline in Harness GitOps by following this guide.
• Visit the Harness Developer Hub for more tutorials and resources.

</TabItem>
</Tabs>