Helm Native Deployment Guide Overview
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.
In this guide:
- Harness Helm or Kubernetes Deployments?
- Blog Post
- Helm Deployments Overview
- Delegate, Providers, and Helm Setup
- Helm Services
- Helm Environments
- Helm Workflows and Deployments
- Helm Troubleshooting
Harness Helm or Kubernetes Deployments?
You can also use Helm with Harness Kubernetes Service and deployments and take advantage of Harness advanced Kubernetes features. See Kubernetes Deployments Overview.
The main difference is that the Helm deployment performed using the Harness Helm Service and described in this guide uses Tiller. If you use Harness Kubernetes Service for deployment, you do not need to use Tiller.
The following blog post walks you through creating a Helm 3 deployment from scratch using Harness, including a video walkthrough:
You can perform all of the steps in this guide using free accounts. You will need a Docker Hub account and a Google Cloud Platform account. Both offer free accounts.
- Developers and DevOps with a working knowledge of Docker, Kubernetes, and Helm.
- Harness users with a working knowledge of the Harness Delegate. For information, see Delegate Installation, Harness Requirements, and Connectivity and Permissions Requirements.
What Are We Going to Do?
This guide walks you through deploying a publicly available Docker image of NGINX to a Google Cloud Platform (GCP) Kubernetes cluster using a publicly available Bitnami Helm chart. Basically, we do the following:
- Docker - Pull a Docker image of NGINX from Docker Hub.
- Helm - Use a Bitnami Helm chart for NGINX from their Github repo and define the Kubernetes service and deployment rules.
- Kubernetes - Deploy to a GCP Kubernetes cluster that is configured with Helm and Tiller.
Sound fun? Let's get started.
What Are We Not Going to Do?
This is a simple guide that covers the basics of deploying Docker images to Kubernetes using Helm. It does not cover the following:
- Ingress Rules - Harness supports Ingress Rules for Kubernetes deployments. You can learn how to use Ingress Rules in Ingress Rules. For a Harness deployment using Helm, you can add Ingress rules in a Helm chart file (kind: Ingress) and Harness will use those during deployment. For information about Ingress rules and Helm, see Secure Kubernetes Services With Ingress, TLS And LetsEncrypt from Bitnami.
What Harness Needs Before You Begin
The following are required to deploy to Kubernetes using Helm via Harness:
- An account with a Docker Artifact Server you can connect to Harness, such as Docker Hub.
- An account with a Kubernetes provider you can connect to Harness, such as Google Cloud Platform.
- Kubernetes Cluster with Helm and Tiller installed and running on one pod.
- Helm chart hosted on a server accessible with anonymous access.
- Harness Delegate installed that can connect to your Artifact Server and Cloud Provider.
We will walk you through the process of setting up Harness with connections to the artifact server and cloud provider, specifications for the Kubernetes cluster, commands for setting up Helm and Tiller on your Kubernetes cluster, and provide examples of a working Helm chart template.