Connect to Your Target Tanzu Account

Updated 2 months ago by Chakravarthy Tenneti

This topic sets up the Harness Delegate in your Tanzu Application Service (TAS, formerly PCF) environment and adds the Cloud Provider used to connect to your Tanzu cloud for deployment.

In this topic:

Before You Begin

Step 1: Set Up the Harness Delegate

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

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

For information on setting up Harness Delegates, see Harness Delegate Overview.

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

Step 2: Add the 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 TAS features you are using in your Harness TAS 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

Using CF CLI 7

Currently, this feature is behind a Feature Flag. Contact Harness Support to enable the feature. Feature Flags can only be removed for Harness Professional and Essentials editions. Once the feature is released to a general audience, it's available for Trial and Community Editions.

See New features added to Harness and Features behind Feature Flags (Early Access) for Feature Flag information.

If you want to use CF CLI 7, ensure you install it on the Harness Delegate using a Delegate Profile and select the Enable CF CLI 7 option when creating the Harness Service.

By default, Harness uses CF CLI 6. Certain CLI commands have been changed between the CLI versions. See Upgrading to CF CLI 7 from Cloud Foundry.

If you enable Enable CF CLI 7, the Harness Delegate will use that CLI version to execute the correct set of commands.

Step 3: Add the Harness TAS Cloud Provider

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

The TAS Cloud Provider has the following settings.

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 TAS 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.

Review: TAS Permissions

Make sure the TAS user account is assigned 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 Tanzu.

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

Next Steps


How did we do?