ahmedelnokaity / helm3

Ressources for "Packaging Applications with Helm for Kubernetes" @ Pluralsight (Helm version 3)

Packaging Applications with Helm for Kubernetes course @ Pluralsight

Ressources for "Packaging Applications with Helm for Kubernetes" @ Pluralsight (Helm version 3)

Install the official Helm chart Repository

helm repo add stable https://charts.helm.sh/stable  

helm repo add stable https://kubernetes-charts.storage.googleapis.com/

Error: repo "https://kubernetes-charts.storage.googleapis.com/" is no longer available; try "https://charts.helm.sh/stable" instead

Install mysql demo

helm install demo-mysql stable/mysql

cleaning Helm

k get all | grep mysql

pod/demo-mysql-8674bf7d9b-98sz8   1/1     Running   0          3m34s
service/demo-mysql   ClusterIP   10.107.127.247   <none>        3306/TCP          3m34s
deployment.apps/demo-mysql   1/1     1            1           3m34s
replicaset.apps/demo-mysql-8674bf7d9b   1         1         1       3m34s

as we can see there are some k8s objects in the cluster including a pod,svc,deployment and there are also some secrets

 k get secret | grep mysql 
demo-mysql                         Opaque                                2      6m21s
sh.helm.release.v1.demo-mysql.v1   helm.sh/release.v1                    1      6m21s

we could of course delete those k8s resources by hand with k delete command but it's not advisable to do so instead we can use the helm uninstall command

helm uninstall demo-mysql
release "demo-mysql" uninstalled
➜  helm3-master k get all | grep mysql   
pod/demo-mysql-8674bf7d9b-98sz8   0/1     Terminating   0          10m

now we can see the pod is terminating

Helm is not very intrusive, it just stores some configs secrets in namespace of your application and deletes them when you uninstall it.

note that is true only for Helm3, Helm 2 is more intrusive with a server side component called Tiller

Helm store some configuration and cache data on the client side

helm env