feat(docs): use helm 3 and other minor fixes (#8)

Author: alexppg

README.md

@@ -10,9 +10,7 @@ The tutorial of "how to create a cluster" is based of this [bitnami tutorial](ht
 
 # The project
 - **chat_front:** Is a simple webpage that sends and receives messages from chat_svc through socket io
-  When you finish this tutorial, you can see this Microservice in 127.0.0.1.nip.io
 - **chat_svc:** Receives messages from chat_front and sends these messages to  chat_db to store this information
-  When you finish this tutorial, you can see this Microservice in svc.127.0.0.1.nip.io
 - **chat_db:** Receives data from chat_svc and stores this information in a SQLite DB.
 
 ## Architecture
@@ -39,6 +37,8 @@ Install Minikube in your local system, either by using a virtualization software
   curl -Lo minikube https://storage.googleapis.com/minikube/releases/vX.Y.Z/minikube-OS_DISTRIBUTION-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/
   ```
 
+  TIP: If you use homebrew you can install it with the brew install command: `brew install minikube`.
+
 ## Step 2: Create A Kubernetes Cluster
 By starting Minikube, a single-node cluster is created. Run the following command in your terminal to complete the creation of the cluster:
 
@@ -47,20 +47,19 @@ minikube start
 ```
 
 
-Install ingress
+Install ingress:
 
 ```
 minikube addons enable ingress
 ```
 
-Set the environment of docker
+Set the environment of docker. This will make you shell use minikube's docker, so any image you build, you'll build it in the minikube machine. With this, you won't need a docker registry:
 ```bash
 eval $(minikube docker-env)
 ```
 
 To run your commands against Kubernetes clusters, the kubectl CLI is needed. Check step 3 to complete the installation of kubectl.
 
-
 ## Step 3: Install The Kubectl Command-Line Tool
 In order to start working on a Kubernetes cluster, it is necessary to install the Kubernetes command line (kubectl). Follow these steps to install the kubectl CLI:
 
@@ -74,7 +73,7 @@ In order to start working on a Kubernetes cluster, it is necessary to install th
 
   TIP: Once the kubectl CLI is installed, you can obtain information about the current version with the kubectl version command.
 
-  NOTE: You can also install kubectl by using the sudo apt-get install kubectl command.
+  NOTE: You can also install kubectl by using the `sudo apt-get install kubectl` command. If you use homebrew you can install it with the brew install command: `brew install kubectl`.
 
 * Check that kubectl is correctly installed and configured by running the kubectl cluster-info command:
 
@@ -101,11 +100,10 @@ In order to start working on a Kubernetes cluster, it is necessary to install th
   ```
   ![Check Kubernetes node info](https://docs.bitnami.com/images/img/platforms/kubernetes/k8-tutorial-33.png)
 
-
 [Learn more about the kubectl CLI](https://kubernetes.io/docs/user-guide/kubectl-overview/).
 
-## Step 4: Install And Configure Helm And Tiller
-The easiest way to run and manage applications in a Kubernetes cluster is using Helm. Helm allows you to perform key operations for managing applications such as install, upgrade or delete. Helm is composed of two parts: Helm (the client) and Tiller (the server). Follow the steps below to complete both Helm and Tiller installation and create the necessary Kubernetes objects to make Helm work with Role-Based Access Control (RBAC):
+## Step 4: Install Helm 
+The easiest way to run and manage applications in a Kubernetes cluster is using Helm. Helm allows you to perform key operations for managing applications such as install, upgrade or delete.
 
 * To install Helm, run the following commands:
 
@@ -115,61 +113,7 @@ The easiest way to run and manage applications in a Kubernetes cluster is using
   ./get_helm.sh
   ```
 
-  TIP: If you are using OS X you can install it with the brew install command: brew install kubernetes-helm.
-
-* Create a ClusterRole configuration file with the content below. In this example, it is named clusterrole.yaml.
-
-  ```yaml
-  apiVersion: rbac.authorization.k8s.io/v1
-  kind: ClusterRole
-  metadata:
-    annotations:
-      rbac.authorization.kubernetes.io/autoupdate: "true"
-    labels:
-      kubernetes.io/bootstrapping: rbac-defaults
-    name: cluster-admin
-  rules:
-  - apiGroups:
-    - '*'
-    resources:
-    - '*'
-    verbs:
-    - '*'
-  - nonResourceURLs:
-    - '*'
-    verbs:
-    - '*'
-  ```
-
-* To create the ClusterRole, run this command:
-
-  ```bash
-  kubectl create -f clusterrole.yaml
-  ```
-  
-* To create a ServiceAccount and associate it with the ClusterRole, use a ClusterRoleBinding, as below:
-
-  ```bash
-  kubectl create serviceaccount -n kube-system tiller
-  kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
-  ```
-
-* Initialize Helm as shown below:
-
-  ```bash
-  helm init --service-account tiller
-  ```
-  If you have previously initialized Helm, execute the following command to upgrade it:
-
-  ```bash
-  helm init --upgrade --service-account tiller
-  ```
-* Check if Tiller is correctly installed by checking the output of kubectl get pods as shown below:
-
-  ```bash
-  kubectl --namespace kube-system get pods | grep tiller
-    tiller-deploy-2885612843-xrj5m   1/1       Running   0   4d
-  ```
+  TIP: If you use homebrew you can install it with the brew install command: `brew install kubernetes-helm`.
 
 Once you have installed Helm, a set of useful commands to perform common actions is shown below:
 
@@ -188,17 +132,21 @@ Create the docker images:
 Check your helm charts:
 
   ```bash
-  helm install --dry-run --debug ./chat_db/chat_db/
-  helm install --dry-run --debug ./chat_svc/chat_svc/
-  helm install --dry-run --debug ./chat_front/chat_front/
+  helm upgrade --dry-run --install chat-front ./chat_front/chat_front/ \
+    --set ingress.enabled=true --set "ingress.hosts[0]=$(minikube ip).nip.io"
+  helm upgrade --dry-run --install chat-svc ./chat_svc/chat_svc/ --set \
+    --set ingress.enabled=true --set "ingress.hosts[0]=svc.$(minikube ip).nip.io"
+  helm upgrade --dry-run --install chat-db ./chat_db/chat_db/
   ```
 
 Install helm charts:
 
   ```bash
-  helm install --name chat-db ./chat_db/chat_db/
-  helm install --name chat-svc ./chat_svc/chat_svc/
-  helm install --name chat-front ./chat_front/chat_front/
+  helm upgrade --install chat-front ./chat_front/chat_front/ \
+    --set ingress.enabled=true --set "ingress.hosts[0]=$(minikube ip).nip.io"
+  helm upgrade --install chat-svc ./chat_svc/chat_svc/ --set \
+    --set ingress.enabled=true --set "ingress.hosts[0]=svc.$(minikube ip).nip.io"
+  helm upgrade --install chat-db ./chat_db/chat_db/
   ```
 
 ## Step 6
@@ -213,33 +161,6 @@ Verify that all pods are Ok:
 
 ## Step 7
 
-Open http://127.0.0.1.nip.io/ and see the magic! ;)
+Open the IP that the command `minikube ip` returns and see the magic! ;)
 
 ![](docs/imgs/front_ms.png)
-
-
-## Troubleshooting
-
-If this URL doesn't work, maybe you need to install a nginx and redirect the traffic from 127.0.0.1 to the minikube IP,
-for example, you can use nginx.
-
-### Way 1: Get your cluster with minikube
-Check your Minikube IP with:
-  ```
-  minikube ip
-  ```
-  
-### Way 2: Get your cluster with kubectl
-
-  ```
-  kubectl cluster-info
-  ```
-![](docs/imgs/kubectl_get_ip.png)
-
-### Add your cluster IP to nginx
-
-- Edit your nginx config with this code as example: See [this example](nginx_example_conf)
-  ```
-  vim /etc/nginx/sites-enabled/default
-  ```
-

chat_front/chat_front/values.yaml

@@ -17,15 +17,12 @@ service:
   port: 80
 
 ingress:
-  enabled: true
+  enabled: false
   annotations: {}
     # kubernetes.io/ingress.class: nginx
     # kubernetes.io/tls-acme: "true"
   paths: ["/"]
-  hosts:
-    - 127.0.0.1.nip.io
-    - 192.168.99.100.nip.io
-    - 192.168.49.2.nip.io
+  hosts: []
   tls: []
   #  - secretName: chart-example-tls
   #    hosts:

chat_svc/chat_svc/values.yaml

@@ -17,14 +17,12 @@ service:
   port: 80
 
 ingress:
-  enabled: true
+  enabled: false
   annotations: {}
     # kubernetes.io/ingress.class: nginx
     # kubernetes.io/tls-acme: "true"
   paths: ["/"]
-  hosts:
-    - svc.127.0.0.1.nip.io
-    - svc.192.168.49.2.nip.io
+  hosts: []
   tls: []
   #  - secretName: chart-example-tls
   #    hosts: