Traditional Deployments Overview
This guide discusses how to perform traditional deployment using application package files and a runtime environment (Tomcat, JBoss) in Harness. These deployments are different from Harness deployments using container orchestration platforms like Kubernetes, Helm, Pivotal Cloud Foundry, Amazon ECS, and Azure.
Traditional deployments involve obtaining an application package from an artifact source, such as a WAR file in an AWS S3 bucket, and deploying it to a target host, such an AWS AMI.
Walk through this guide in the following order:
- Deployment Summary
- Supported Packaging Formats
- Delegate, Providers, and Connectors Setup
- Services for App Packages
- App Stacks and Default Variables
- Commands and Scripts
- Environments for Traditional Deployments
- Traditional Workflows and Deployments
The following list describes the major steps we will cover in this guide:
- Installing the Harness Delegate in your target infrastructure.
- Add an Artifact Server. In this guide, we will use an AWS S3 bucket containing the file we want to deploy.
- Add a Cloud Provider. This is a connection to your deployment infrastructure, either physical or hosted in a cloud platform like AWS, GCP, or Azure.
- Create the Harness Application for your deploying your file(s). The Harness Application represents a group of microservices, their deployment pipelines, and all the building blocks for those pipelines. Harness represents your deployment using a logical group of one or more entities: Services, Environments, Workflows, Pipelines, Triggers, and Infrastructure Provisioners. Applications organize all of the entities and configurations in Harness CD.
- Create the Harness Service using the SSH type.
- Add your packaged application file(s) as an Artifact Source.
- Create the Harness Environment containing the Service Infrastructure definition of your deployment infrastructure.
- Create the Basic Deployment Workflow.
- Deploy the Workflow.
- Advanced options not covered in this guide:
- Create a Harness Pipeline for your deployment, including Workflows and Approval steps. For more information, see Pipelines.
- Create a Harness Trigger to automatically deploy your Workflows or Pipeline according to your criteria. For more information, see Triggers.
- Create Harness Infrastructure Provisioners for your deployment environments. For more information, see Infrastructure Provisioners.
Supported Packaging Formats
Harness supports the following traditional deployment packaging formats: WAR, JAR, TAR, RPM, ZIP, Docker, and custom files.
All of these formats are also supported by other Harness deployment types, such as Kubernetes, Helm, PCF, ECS, etc. This guide is concerned with traditional deployments outside of the container orchestration platforms.