Deploy the app with Helm Charts

Helm helps you manage Kubernetes applications — Helm Charts helps you define, install, and upgrade even the most complex Kubernetes application.

During this lab, we are going to install a helm client and configure it. Then we are going to deploy the same app with Helm.

Charts are easy to create, version, share, and publish — so start using Helm and stop the copy-and-paste madness.

Helm is a client/server application :

Helm client
Tiller server.

Initialize Helm & Tiller

Initialize Helm by navigating and running the below command in your cluster

 helm init

Results:

 $ helm init
 $HELM_HOME has been configured at /Users/mace/.helm.

 Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.

 Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
 For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
 Happy Helming!

Verify that the tiller-deploy pod has a Status of Running in your cluster.

 kubectl get pods -n kube-system -l app=helm

Results:

 NAME                           READY     STATUS    RESTARTS   AGE
 tiller-deploy-75f5797b-sxmrq   1/1       Running   0          4m

Deploy the app with Helm

Go to the folder kubernetes/helm/chart
```
 cd mytodo/chart/mytodos
```

Edit the file values.yaml to change the repository values which includes: the region, the registry namespace, the image name, and the tag (=version).

 > repository region = us and namespace = pyrk8s

 > cluster region = us-south

 ```yaml
   # Default values for mytodos.
   # This is a YAML-formatted file.
   # Declare variables to be passed into your templates.

 replicaCount: 3

 image:
   repository: <region>.icr.io/<namespace>/todo-<lastname>
   tag: "1.0"
   pullPolicy: Always

  # secret:
  #   database: database-credentials

 nameOverride: ""
 fullnameOverride: ""

 service:
   type: ClusterIP
   port: 8080

 ingress:
   enabled: true
   annotations:
     # Force the use of https if the request is http
     ingress.bluemix.net/redirect-to-https: "True"
 path: /
 hosts:
     - todo.<cluster-name>.<region>.containers.appdomain.cloud
 tls:
     - secretName: <cluster-name>
     hosts:
         - todo.<cluster-name>.<region>.containers.appdomain.cloud

 resources:
   # We usually recommend not to specify default resources and to leave this as a conscious
   # choice for the user. This also increases chances charts run on environments with little
   # resources, such as Minikube. If you do want to specify resources, uncomment the following
   # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
 limits:
     cpu: 500m
     memory: 384Mi
 requests:
     cpu: 250m
     memory: 128Mi

 nodeSelector: {}

 tolerations: []

 affinity: {}

Helm runs with "default" service account. Set the right permissions to be able to install package
```
 kubectl create clusterrolebinding add-on-cluster-admin --clusterrole=cluster-admin --serviceaccount=kube-system:default
```
Installing package will throw this error if you don't have the correction permission: Error: UPGRADE FAILED: configmaps is forbidden

Install a Helm chart

 helm upgrade mytodos . --install

Results:

 NAME:   mytodos
 LAST DEPLOYED: Fri Nov 16 18:51:12 2018
 NAMESPACE: default
 STATUS: DEPLOYED

 RESOURCES:
 ==> v1/Service
 NAME     TYPE       CLUSTER-IP     EXTERNAL-IP  PORT(S)   AGE
 mytodos  ClusterIP  172.21.52.118  <none>       8080/TCP  0s

 ==> v1beta2/Deployment
 NAME     DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
 mytodos  3        3        3           0          0s

 ==> v1beta1/Ingress
 NAME     HOSTS                                            ADDRESS           PORTS    AGE
 mytodos  todo.lab-cluster-1.eu-de.containers.appdomain.cloud  149.81.67.38,...  80, 443  0s

 ==> v1/Pod(related)
 NAME                      READY  STATUS             RESTARTS  AGE
 mytodos-86884779d9-4c62z  0/1    ContainerCreating  0         0s
 mytodos-86884779d9-jzzpt  0/1    ContainerCreating  0         0s
 mytodos-86884779d9-qxnt2  0/1    ContainerCreating  0         0s

Get the status of the helm deployment
```
 helm status mytodos
```
Get the application URL by running these commands:
```
 https://todo.<cluster-name>.eu-de.containers.appdomain.cloud/
```
To run with local values in debug mode: helm install . --name mytodos --values=local-values.yaml --dry-run --debug

Delete your deployment

To delete your deployment
```
 helm delete --purge mytodos
```
Generally, an helm chart is managing many pods, deployments, secrets, volumes and services. So deleting the chart is a quick way to clean up your work.

results matching ""

No results matching ""