Harness Connected On-Premise Setup

Updated 2 months ago by Michael Cretzman

This document describes the process for setting up Harness Connected On-Premise.

For more information about Harness Connected On-Premise, see Harness Architecture and On-Premise Overview.

Intended Audience

  • System Administrators
  • Network Administrators
  • DevOps

Installation Overview

The Harness platform comprises 5 micro-services:

  • Proxy/Load Balancer
  • User Interface
  • Machine Learning Engine
  • Manager
  • Database

Each micro-service is containerized and is deployed on every physical machine.

Once you are signed up with Harness, you download and install an Ambassador that acts as a proxy between your data center and Harness.io. The Ambassador makes one-way outbound HTTPS calls to Harness.io, initiates the on-premise installation across your physical machines, and automates the Harness Connected On-Premise installation process for you.

Harness Connected On-Premises installation is managed by Harness Support and takes minutes.

The high-level steps for obtaining Harness Connected On-Premise are:

  1. Prepare your on-premise infrastructure for Harness.
  2. Provide Harness with your infrastructure information via email.
  3. Download and run the Ambassador, the tool Harness uses to initiate your Harness Connected On-Premise deployment, and notify Harness that the Ambassador is running.
  4. Harness triggers the installation and notifies you.
  5. Point your browser at the URL for your Connected Harness On-Premise.
  6. Download the Harness delegate and begin setup.

Set Up Harness Connected On-Premise

To set up Harness Connected On-Premise, do the following:

  1. Prepare your on-premise infrastructure for Harness. There are separate requirements for Harness Connected On-Premise Evaluation and Harness Connected On-Premise Production.
    For the requirements, see Harness On-Premise Evaluation Requirements and Harness On-Premise Production Requirements.
  2. Once your infrastructure is configured, send the infrastructure information to Harness Support at support@harness.io with the subject Harness On-Premise Information.
    Use the following list to enter your information and paste it into your email:
    • Company Name*:
    • Account Name:
    • Primary Admin Email Address*:
    • Host 1 IP Address (Private IP)*:
    • Host 2 IP Address (Private IP)**:
    • Host 3 IP Address (Private IP)**:
    • Load Balancer URL (including https:// scheme)**:
    • SSH Username*:
    • SSH Key File Path*:
    SSH interconnectivity is required among all three hosts. The SSH Key must be present on all machines so they may connect to each other.
  3. Harness support will make an account entry in the Harness cloud based on the information you sent and then provide you with an URL for the Ambassador download.
  4. Run the Ambassador on any one machine. After receiving the Ambassador download URL from Harness Support, perform the following steps on one or more of the hosts you provided to Harness.
    1. Download the Ambassador using curl.
    2. Expand the archive.
    3. Start the Ambassador: $./start.sh
  5. Once the Ambassador is up and running, notify Harness Support at support@harness.io or the sales representative you are working with about your on-premise setup.
  6. Using Ambassador, Harness Support will initiate the deployment of your version of Connected Harness On-Premise onto your infrastructure.

Harness On-Premise Evaluation Requirements

Harness On-Premise Evaluation has the following requirements.

Component

Description

System

1 Linux Machine:

  • 8 cores, 32GB Memory, 250GB Disk
  • Packages: Docker, cURL, unzip, sed

Firewall Rules

Internal Source: Application Subnet

  • Destination: Harness Machine/Subnet
  • Port 7143 (HTTPS)
  • Protocol: TCP

External Source: Harness Machine/Subnet

  • Destination: app.harnes.io
  • Port 443 (HTTPS)
  • Protocol: TCP

External Source: Docker Hub

  • Destination: hub.docker.com
  • Port 443 (HTTPS)
  • Protocol: TCP

Harness On-Premise Production Requirements

Harness On-Premise Production has the following requirements.

Component

Description

System

3 Linux Machine:

  • 16 cores, 32GB Memory, 250GB Disk
  • Packages: Docker, cURL, unzip, sed
  • SSH Keyless setup among machines

Load Balancer

SSL Certificates installed

Firewall Rules

Internal Source: Application Subnet

  • Destination: Load Balancer
  • Port 443 (HTTPS)
  • Protocol: TCP

Internal Source: Load Balancer
(harness.your_company.com)

  • Destination: Machines/Subnet
  • Port 7143 (HTTPS)
  • Protocol: TCP

Internal Source: Harness Machine/Subnet

  • Destination: Machines/Subnet (within subnet)
  • Port 7143-7153 (HTTPS)
  • Protocol: TCP

External Source: Harness Machine/Subnet

  • Destination: app.harnes.io
  • Port 443 (HTTPS)
  • Protocol: TCP

External Source: Docker Hub

Destination: hub.docker.com

Port 443 (HTTPS)

Protocol: TCP

Notes

The delegate is installed in your network and connects to Harness Connected On-Premise. The delegate has the following requirements:

  • Linux/UNIX server
  • Minimum 6GB RAM
  • Minimum 6GB Disk Space
  • Access to artifact servers, deployment environments, and cloud providers
  • Multiple delegates can be used and their scope can be managed.
  • The Harness delegate does NOT require root account access.


How did we do?