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 Deployment
- Lambda Deployments
- Traditional Deployments
More deployment documents will be added to the documentation soon.
Kubernetes or Helm?
Harness includes both Kubernetes and Helm deployments, and you can 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.
- 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.