New Features and Info
- AWS Elastic Container Service (ECS) Deployment
- 24x7 Service Guard
- Harness GitOps
- File-based Repo Triggers
- Harness Connected On-Premise Setup
- Configuration as Code (GitOps)
- Variables and Expressions in Harness
- Passing Variables into Workflows and Pipelines from Triggers
- Using the Jenkins Command
- Using the Shell Script Command
- Pivotal Cloud Foundry Deployment
- IIS (.NET) Azure and AWS Deployment
- Docker, Kubernetes, and Helm Deployment
- SSH over Kerberos
- Your Verification Provider is Supported
- Single Sign-On (SSO) with SAML
- Single Sign-On (SSO) with LDAP
- Terraform Remote State
- Kubernetes and Harness FAQ
- Template Library
- Harness Quick Start Setup Guide
- Tour the Harness Platform
AWS Elastic Container Service (ECS) Deployment
Learn how to use AWS Amazon Elastic Container Service (ECS) with Harness: set up Harness for ECS, create a Harness Application, and deploy a public Docker image from Docker Hub to an existing ECS cluster using Harness.
24x7 Service Guard
Harness 24x7 Service Guard gives DevOps operational visibility across all their monitoring tools in all their deployment environments.
See 24x7 Service Guard.
Harness enables a developer-centric experience for managing applications by implementing the GitOps methodology across its components.
See Harness GitOps.
File-based Repo Triggers
In some Webhook trigger scenarios, you might set a Webhook on your repo to trigger a Workflow or Pipeline when a Push event occurs in the repo. However, you might want to initiate the trigger only when specific files in the repo are changed.
Harness Connected On-Premise Setup
In the Harness on-premise offering, the Harness Manager runs in your enterprise cloud environment and Harness manages the installation through a connection to Harness' cloud.
Configuration as Code (GitOps)
Everything you can do in the Harness platform GUI, you can do in YAML:
- Using the Harness code editor, you can set up and manage accounts for artifact servers, cloud providers, and verification providers. You can edit application services, environments, workflows, etc, all in YAML.
- You can sync your Git repo with Harness to simply use YAML files in your source repo to make changes to Harness.
Variables and Expressions in Harness
Harness includes two types of variables you can use:
- Harness built-in variables: There are variables scoped to different entities, such as applications, services, environments, workflows, and variables that provide information about deployment environments, such as the host name of the host where a microservice is deployed.
- User-created variables: You can create variables at the account-level and application-level that can be used across your Harness applications, and create variables in application entities to be replaced by users when configuring or deploying a CD pipeline.
Passing Variables into Workflows and Pipelines from Triggers
You can pass variables from a Harness trigger into a Harness workflow to be used during workflow steps or configuration, or as part of a pipeline. This process can be valuable when you want to use information from the condition that initiated the trigger as settings in your workflow at runtime.
Using the Jenkins Command
With the Jenkins command, you can execute Jenkins jobs in the shell session of the workflow.
When executing a job, you can also dynamically capture the output from the job, publishing runtime variables based on the context, and using those variables in another step in the same workflow, phase, or another workflow or phase in the same pipeline.
Using the Shell Script Command
With the Shell Script command, you can execute scripts in the shell session of the workflow in the following ways:
- Execute bash or PowerShell scripts on the host running a Harness Delegate. You can use Tags to identify which Harness delegate to use.
- Execute bash or PowerShell scripts on a remote host in the deployment service infrastructure.
Pivotal Cloud Foundry Deployment
Harness provides support for the Pivotal Cloud Foundry (PCF) app development and deployment platform for public and private clouds.
IIS (.NET) Azure and AWS Deployment
Harness provides support for Microsoft IIS and .NET for Azure and AWS deployments.
Docker, Kubernetes, and Helm Deployment
This guide will walk you through deploying a Docker image to a Kubernetes cluster using a Helm chart. This deployment scenario is very popular and a walkthrough of all the steps involved will help you set up this scenario in Harness for your own microservices and apps.
SSH over Kerberos
Harness supports SSH server authentication using Kerberos, enabling you to SSH into a target host via the Kerberos protocol.
See SSH via Kerberos.
Your Verification Provider is Supported
Harness supports all of the most popular verification providers.
Single Sign-On (SSO) with SAML
Harness supports Single Sign-On (SSO) with SAML, integrating with your SAML SSO provider to enable you to log your users into Harness as part of your SSO infrastructure.
Single Sign-On (SSO) with LDAP
Harness supports Single Sign-On (SSO) with LDAP, such as Active Directory and OpenLDAP, integrating with your LDAP directory to enable you to log your LDAP users into Harness as part of Harness SSO infrastructure.
Terraform Remote State
You can map the variables used by the remote_state command in your configuration file into the Backend Configuration (Remote state) section of the Terraform Provisioner dialog.
Kubernetes and Harness FAQ
This FAQ answers all of the common questions about Harness integration with Kubernetes, how Harness deploys to Kubernetes clusters and pods, and how you can customize Harness to your desired Kubernetes orchestration.
You can use the Template Library to create template entities and copy or link them into services and workflows. If you link to a template and it is updated in the Template Library, the new changes are automatically in the services and workflows using the template. Templates are versioned and you can select which version you want to use or link to.
See Use Templates.
Harness Quick Start Setup Guide
This guide takes you through a simple Harness deployment setup quickly (approximately 30min). The guide uses a publicly available Tomcat artifact off of Docker Hub and, using Harness, deploys it to the Google Cloud Platform (GCP). You can use a free trial account of GCP or your existing account. The goal of the guide is to show you the flow of setting up Harness.
Tour the Harness Platform
if you're new to the Harness Platform UI, this topic will take you through the major pages and elements.