Sign in
Globalcorp

Step 2 of 7

Deploy Software

Globalcorp - Deploy Software

Updated Sep 16, 2026 · Harness Admin

Platform Concept: Platform Integrations

  • With an artifact ready to go, we'll build a deployment pipeline leveraging Harness scriptless cloud platform integrations.

A) Create a service definition

  1. In the left nav, click Project Settings, then services, then New Service.

  2. Follow the table to configure:

    Name

    Text
    catalogapi

    save

    Service definition

    Kubernetes

    Manifests

  3. Click +Add Manifest

  4. Click K8s Manifest Continue

  5. Click Code

    Continue

    Manifest Identifier

    Text
    catalogapi_kubernetes

    File/Folder Path

  6. Click Repository Name, then catalogapi-norefs.

  7. Use main for the branch, then the following for File/Folder Path

    Text
    service/manifest.yaml

    Values.yaml

  8. Click +Add File.

  9. Use the following Path

    Text
    service/values.yaml

    GC Deploy

    Artifacts

  10. Click Add Artifact Source

  11. Click Artifact Registry

    Continue

  12. Use catalog_api_artifact for the Artifact Source Identifier.

  13. Select your project's registry, then Apply Selected.

  14. Use catalogapi for Package Name.

  15. For the tag, use:

    Text
    <+project.identifier>

    GC Deploy

  16. Click Save! (top right)

B) Build CD Stage

  1. In the left nav, click Pipelines, then open the Software Delivery Fastlane pipeline you created in the previous step.

  2. Click + above Add Stage, then click Deploy.

  3. For Stage Name, enter Deploy Software, then click Kubernetes deployment type below.

  4. Click Select Service, then catalogapi

    GC Build

    Continue

  5. For Specify Environment, click box, then organization then Production Environment.

    GC Build

  6. For Infrastructure, click box, then your kubernetes infrastructure.

    Continue

  7. For Execution straegies, click Canary

    GC Deploy

    save

  1. Click Run, then Run Pipeline.
  2. When complete, switch to google cloud, find service kubernetes engine, and review your deployed services.
  3. (Optional) On the pipeline execution, click the get services step. Put the public IP address into your browser and add :8080. You'll see a valid 200 response from your new service!

C) Revenge of the Servicenow Template! OOOoOO!

  1. (Optional) In Harness, click the Ticketing stage, then Create Ticket.

  2. (Optional) Find the ticketNumber line, and hover to get a copy button- then click.

    GC Deploy

  3. Click on Edit Pipeline in the top right corner.

  4. Select the 'nonprod kubernetes' stage.

  5. Hover your cursor right between the canary stages and click the + sign that appears.

    GC Deploy

  6. Click Add Step, then select ServiceNow Approval.

  7. Follow the table to configure:

    Name

    Text
    ServiceNow Approval

    ServiceNow Connector

    Text
    Global Servicenow Connector (in your project)

    GC Build

    Ticket Type

    Text
    Change Request

    Ticket Number

    Text
    <+pipeline.stages.Ticketing.spec.execution.steps.Create_Ticket.ticket.ticketNumber>

    Retry interval

    Text
    10s

    Approval Criteria

    Field State, Operator =, Value Implement

    GC Build

    save

  8. Click on the Servicenow Approval step, then click Save as Template top right.

  9. Name the template Servicenow Approval, give it a version of 1

    save

  10. Click Yes when asked to use the template. Click Apply Changes top right.

    save

  11. Click Run and Run Pipeline. When it pauses for Servicenow Approval, switch to your google cloud tab to see your canary release.

  12. Back in Harness, click on the change to follow the Servicenow link. Move the change to review and confirm Harness finishes the deployment only when approved.