1 - Delegate and Connectors for PCF

Updated 5 months ago by Michael Cretzman

This topic sets up the Harness Delegate in your PCF environment, Artifact Server to connect to your artifact repo, and the Cloud Provider used to connect to your PCF cloud for deployment.

In this topic:

Harness Delegate

The Harness Delegate is a service you run in your local network or VPC to connect your artifact servers, PCF infrastructure, and any other providers with the Harness Manager.

If you are running your PCF Cloud in AWS, you can use a Shell Script Delegate run on an EC2 instance in the same VPC and subnet as your PCF Cloud, or an ECS Delegate run in an ECS cluster in the same VPC.

For information on setting up Harness Delegates, see Delegate Installation and Management.

If you want to install the CF CLI on the Delegate, use a Harness Delegate Profile and the script shown in Cloud Foundry CLI.

Cloud Foundry CLI

The host running the Harness Delegate must run the CF CLI in order to execute the required commands.

Follow the steps in Installing the cf CLI from Pivotal to install the CLI. You can also use a Delegate Profile to install the CLI, as described in Delegate Profiles and Cloud Foundry CLI.

The version of the CF CLI you install on the Delegate should always match the PCF features you are using in your Harness PCF deployment. For example, if you are using buildpacks in your manifest.yml in your Harness Service, the CLI you install on the Delegate should be version 3.6 or later.

Here is an example Delegate Profile that installs the CF CLI:

apt-get install wget
wget -q -O - https://packages.cloudfoundry.org/debian/cli.cloudfoundry.org.key | apt-key add -
echo "deb https://packages.cloudfoundry.org/debian stable main" | tee /etc/apt/sources.list.d/cloudfoundry-cli.list
apt-get update
apt-get install cf-cli

PCF Cloud Provider

A Harness PCF Cloud Provider connects Harness to your PCF account and allows the Harness Delegate to make API calls.

The Pivotal Cloud Foundry dialog has the following fields.



Display Name

Enter a name for the Cloud Provider. You will use this name when selecting this Cloud Provider in Harness Infrastructure Definitions.

Endpoint URL

Enter the API endpoint URL, without URL scheme. For example, api.run.pivotal.io. Omit http://.For more information, see Identifying the API Endpoint for your PAS Instance from Pivotal.

Username / Password

Username and password for the PCF account to use for this connection.

Usage Scope

If you want to restrict the use of a provider to specific applications and environments, do the following:

In Usage Scope, click the drop-down under Applications, and click the name of the application.

In Environments, click the name of the environment.

PCF Permissions

PCF user account with Admin, Org Manager, or Space Manager role. The user account must be able to update spaces, orgs, and applications.

For more information, see Orgs, Spaces, Roles, and Permissions from Pivotal.

For steps on setting up all Cloud Providers, see Add Cloud Providers.

Artifact Server

Harness integrates with many different types of repositories and artifact providers. We call these Artifact Servers, and they help you pull your artifacts into your Harness Applications.

Once you set up an Artifact Server, Harness can pull artifacts and add them to the Harness Service you will deploy to PCF.

For steps on setting up an Artifact Server, Add Artifact Servers.

Next Step

How did we do?