The deployment guides walk you through setting up a specific deployment using Harness, such as ECS, Kubernetes, and Helm. They are written to provide you with everything you need to learn how to model your CD process in Harness.
In this topic:
- Deployment Guides
- Kubernetes or Helm?
- Harness and AWS Video Summary
- Harness and Microsoft .NET and Azure Video Summary
- Canary Deployment Video Summary
The following articles will walk you through how Harness implements common deployments according to platforms and scenarios:
- AMI (Amazon Machine Image) Deployment
- AWS Elastic Container Service (ECS) Deployment
- Azure Deployments
- Helm Deployments
- IIS (.NET) Deployment
- Kubernetes Deployments
- Pivotal Cloud Foundry Deployments
- Lambda Deployments
- Traditional Deployments
- Artifact Build and Deploy Deployments
More deployment documents will be added to the documentation soon.
Kubernetes or Helm?
Harness includes both Kubernetes and Helm deployments, and you can use Helm charts in both. Here's the difference:
- Harness Kubernetes Deployments allow you to use your own Kubernetes manifests or a Helm chart (remote or local), and Harness executes the Kubernetes API calls to build everything without Helm and Tiller needing to be installed in the target cluster.
Harness Kubernetes deployments also support all deployment strategies (Canary, Blue/Green, Rolling, etc).
- For Harness Helm Deployments, you must always have Helm and Tiller running on one pod in your target cluster. Tiller makes the API calls to Kubernetes in these cases.
Harness Helm deployments only support Basic deployments.
Harness and AWS Video Summary
The following video provides a summary of Harness integration with AWS Marketplace and AWS compute and container services.
Harness and Microsoft .NET and Azure Video Summary
Here is a quick primer on deploying Microsoft IIS .NET applications and Microsoft .NET Core container applications using Harness Continuous Delivery.