added final demos

Author: JaimeSalas

04-cloud/01-eks/05-helm/01-install-helm.md

@@ -0,0 +1,41 @@
+# Install Helm CLI
+
+## Introduction
+
+[Helm](https://helm.sh/) is a package manager and application management tool for Kubernetes that packages multiple Kubernetes resources into a single logical deployment unit called a Chart.
+
+* Helm helps you to:
+  - Achieve a simple (one command) and repeatable deployment
+  - Manage application dependency, using specific versions of other application and services
+  - Manage multiple deployment configurations: test, staging, production and others
+  - Execute post/pre deployment jobs during application deployment
+  - Update/rollback and test application deployments
+
+
+## Installing Helm
+
+Before we can get started configuring Helm, we'll need to first install the command line tools.
+
+```bash
+$ curl -sSL https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash
+```
+
+We can verify the installation by
+
+```bash
+$ helm version --short
+```
+
+Let’s configure our first Chart repository. Chart repositories are similar to APT or yum repositories that you might be familiar with on Linux, or Taps for Homebrew on macOS.
+
+Download the `stable` repository so we have something to start with:
+
+```bash
+helm repo add stable https://charts.helm.sh/stable
+```
+
+Once this is installed, we will be able to list the charts you can install:
+
+```bash
+$ helm search repo stable
+```

04-cloud/01-eks/05-helm/02-deploy-nginx-with-helm.md

@@ -0,0 +1,213 @@
+# Deploy nginx with Helm
+
+## Update the Chart Repository
+
+Helm uses a packaging format called [Charts](https://helm.sh/docs/topics/charts/). A Chart is a collection of files and templates that describes Kubernetes resources.
+
+Charts can be simple, describing something like a standalone web server (which is what we are going to create), but they can also be more complex, for example, a chart that represents a full web application stack, including web servers, databases, proxies, etc.
+
+Instead of installing Kubernetes resources manually via `kubectl`, one can use Helm to install pre-defined Charts faster, with less chance of typos or other operator errors.
+
+Chart repositories change frequently due to updates and new additions. To keep Helm’s local list updated with all these changes, we need to occasionally run the [repository update](https://helm.sh/docs/helm/helm_repo_update/) command.
+
+To update Helm's local list of Charts, run:
+
+```bash
+# first, add the default repository, then update
+helm repo add stable https://charts.helm.sh/stable
+helm repo update
+
+``` 
+
+## Search Chart Repositories
+
+Now that our repository Chart list has been updated, we can [search for Charts](https://helm.sh/docs/helm/helm_search/)
+
+To list all Charts:
+
+```bash
+$ helm search repo
+```
+
+You can see from the output that it dumped the list of all Charts we have added. In some cases that may be useful, but an even more useful search would involve a keyword argument. So next, we’ll search just for nginx:
+
+```bash
+$ helm search repo nginx
+```
+
+The results in:
+
+```
+NAME                            CHART VERSION   APP VERSION     DESCRIPTION                                       
+stable/nginx-ingress            1.41.3          v0.34.1         DEPRECATED! An nginx Ingress controller that us...
+stable/nginx-ldapauth-proxy     0.1.6           1.13.5          DEPRECATED - nginx proxy with ldapauth            
+stable/nginx-lego               0.3.1                           Chart for nginx-ingress-controller and kube-lego  
+stable/gcloud-endpoints         0.1.2           1               DEPRECATED Develop, deploy, protect and monitor...
+```
+
+This new list of Charts are specific to nginx, because we passed the **nginx** argument to the `helm search repo` command.
+
+> Reference: https://helm.sh/docs/helm/helm_search_repo/
+
+## Add the Bitnami Repository
+
+We saw that nginx offers many different products via the default Helm Chart repository, but the nginx standalone web server is not one of them.
+
+After a quick web search, we discover that there is a Chart for the nginx standalone web server available via the [Bitnami Chart repository](https://github.com/bitnami/charts/tree/master/bitnami).
+
+
+```bash
+$ helm repo add bitnami https://charts.bitnami.com/bitnami
+```
+
+Once that completes, we can search all Bitnami Charts:
+
+```bash
+helm search repo bitnami
+
+```
+
+Search once again for nginx
+
+```bash
+$ helm search repo nginx
+```
+
+Now we are seeing more nginx options, across both repositories:
+
+```
+bitnami/nginx                           8.2.3           1.19.6          Chart for the nginx server                        
+bitnami/nginx-ingress-controller        7.0.5           0.41.2          Chart for the nginx Ingress controller            
+stable/nginx-ingress                    1.41.3          v0.34.1         DEPRECATED! An nginx Ingress controller that us...
+```
+
+Or even search the Bitnami repo, just for nginx:
+
+```bash
+$ helm search repo bitnami/nginx
+
+```
+
+## Install bitnami/nginx
+
+Installing the Bitnami standalone nginx web server Chart involves us using the [helm install](https://helm.sh/docs/helm/helm_install/) command.
+
+A Helm Chart can be installed multiple times inside a Kubernetes cluster. This is because each installation of a Chart can be customized to suit a different purpose.
+
+For this reason, you must supply a unique name for the installation, or ask Helm to generate a name for you.
+
+```bash
+$ helm install mywebserver bitnami/nginx --dry-run
+```
+
+Now to really install nginx on our cluster, we can run:
+
+```bash
+$ helm install mywebserver bitnami/nginx
+```
+
+The output is simillar to this
+
+```bash
+NAME: mywebserver
+LAST DEPLOYED: Mon Dec 21 15:45:05 2020
+NAMESPACE: default
+STATUS: deployed
+REVISION: 1
+TEST SUITE: None
+NOTES:
+** Please be patient while the chart is being deployed **
+
+NGINX can be accessed through the following DNS name from within your cluster:
+
+    mywebserver-nginx.default.svc.cluster.local (port 80)
+
+To access NGINX from outside the cluster, follow the steps below:
+
+1. Get the NGINX URL by running these commands:
+
+  NOTE: It may take a few minutes for the LoadBalancer IP to be available.
+        Watch the status with: 'kubectl get svc --namespace default -w mywebserver-nginx'
+
+    export SERVICE_PORT=$(kubectl get --namespace default -o jsonpath="{.spec.ports[0].port}" services mywebserver-nginx)
+    export SERVICE_IP=$(kubectl get svc --namespace default mywebserver-nginx -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
+    echo "http://${SERVICE_IP}:${SERVICE_PORT}"
+```
+
+In order to review the underlying Kubernetes services, pods and deployments, run:
+
+```bash
+$ kubectl get svc,po,deploy
+
+NAME                        TYPE           CLUSTER-IP     EXTERNAL-IP                                                              PORT(S)        AGE
+service/kubernetes          ClusterIP      10.100.0.1     <none>                                                                   443/TCP        136m
+service/mywebserver-nginx   LoadBalancer   10.100.9.232   a7130a0207757453594c4cb5bdf072e5-381544302.eu-west-3.elb.amazonaws.com   80:31519/TCP   2m38s
+
+NAME                                     READY   STATUS    RESTARTS   AGE
+pod/mywebserver-nginx-857766d4fd-9tdwf   1/1     Running   0          2m37s
+
+NAME                                READY   UP-TO-DATE   AVAILABLE   AGE
+deployment.apps/mywebserver-nginx   1/1     1            1           2m38s
+```
+
+The first object shown in this output is a Deployment. A Deployment object manages rollouts (and rollbacks) of different versions of an application.
+
+You can inspect this Deployment object in more detail by running the following command:
+
+```bash
+$ kubectl describe deployment mywebserver
+
+```
+
+The next object shown created by the Chart is a Pod. A Pod is a group of one or more containers.
+
+To verify the Pod object was successfully deployed, we can run the following command:
+
+```bash
+$ kubectl get pods -l app.kubernetes.io/name=nginx
+
+NAME                                 READY   STATUS    RESTARTS   AGE
+mywebserver-nginx-857766d4fd-9tdwf   1/1     Running   0          4m48s
+
+```
+The third object that this Chart creates for us is a Service. A Service enables us to contact this nginx web server from the Internet, via an Elastic Load Balancer (ELB).
+
+To get the complete URL of this Service, run:
+
+```bash
+$ kubectl get service mywebserver-nginx -o wide
+
+NAME                TYPE           CLUSTER-IP     EXTERNAL-IP                                                              PORT(S)        AGE     SELECTOR
+mywebserver-nginx   LoadBalancer   10.100.9.232   a7130a0207757453594c4cb5bdf072e5-381544302.eu-west-3.elb.amazonaws.com   80:31519/TCP   6m22s   app.kubernetes.io/instance=mywebserver,app.kubernetes.io/name=nginx
+```
+
+Copy the value for EXTERNAL-IP, open a new tab in your web browser, and paste it in.
+
+## Clean up
+
+To remove all the objects that the Helm Chart create we can use [helm uninstall](https://helm.sh/docs/helm/helm_uninstall/)
+
+Before we uninstall our application, we can verify what we have running via the [helm list](https://helm.sh/docs/helm/helm_list/) command:
+
+```bash
+$ helm list
+WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/lemoncode/.kube/config
+WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/lemoncode/.kube/config
+NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART           APP VERSION
+mywebserver     default         1               2020-12-21 15:45:05.835403883 +0100 CET deployed        nginx-8.2.3     1.19.6 
+```
+
+To uninstall:
+
+```bash
+$ helm uninstall mywebserver
+
+```
+
+kubectl will also demonstrate that our pods and service are no longer available:
+
+```bash
+kubectl get pods -l app.kubernetes.io/name=nginx
+kubectl get service mywebserver-nginx -o wide
+
+``` 

04-cloud/01-eks/06-autoscalling-our-applications/00-install-kube-ops-view.md

@@ -0,0 +1,41 @@
+# Install Kube-ops-view
+
+Before starting to learn about the various auto-scaling options for your EKS cluster we are going to install Kube-ops-view.
+
+Kube-ops-view provides a common operational picture for a Kubernetes cluster that helps with understanding our cluster setup in a visual way.
+
+> Note: helm must be installed
+
+The following line updates the stable helm repository and then installs kube-ops-view using a LoadBalancer Service type and creating a RBAC (Resource Base Access Control) entry for the read-only service account to read nodes and pods information from the cluster.
+
+```bash
+helm install kube-ops-view \
+stable/kube-ops-view \
+--set service.type=LoadBalancer \
+--set rbac.create=True
+
+```
+
+The execution above installs kube-ops-view exposing it through a Service using the LoadBalancer type. A successful execution of the command will display the set of resources created and will prompt some advice asking you to use `kubectl proxy` and a local URL for the service. Given we are using the type LoadBalancer for our service, we can disregard this; Instead we will point our browser to the external load balancer.
+
+> Monitoring and visualization shouldn’t be typically be exposed publicly unless the service is properly secured and provide methods for authentication and authorization. You can still deploy kube-ops-view using a Service of type ClusterIP by removing the --set service.type=LoadBalancer section and using kubectl proxy. Kube-ops-view does also support Oauth 2
+
+To check the chart was installed successfully:
+
+```bash
+helm list
+WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/lemoncode/.kube/config
+WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/lemoncode/.kube/config
+NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
+kube-ops-view   default         1               2020-12-21 16:29:18.677926812 +0100 CET deployed        kube-ops-view-1.2.4     20.4.0    
+```
+
+With this we can explore kube-ops-view output by checking the details about the newly service created.
+
+```bash
+kubectl get svc kube-ops-view | tail -n 1 | awk '{ print "Kube-ops-view URL = http://"$4 }'
+
+```
+
+This will display a line similar to Kube-ops-view URL = http://<URL_PREFIX_ELB>.amazonaws.com Opening the URL in your browser will provide the current state of our cluster.
+

04-cloud/01-eks/06-autoscalling-our-applications/01-scale-an-application-with-HPA.md

@@ -0,0 +1,97 @@
+# Scale an aplication with HPA
+
+## Configure Horizontal Pod Autoscaler (HPA)
+
+### Deploy the Metrics Server
+
+Metrics Server is a scalable, efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.
+
+These metrics will drive the scaling behavior of the *deployments*.
+
+We will deploy the metrics server using [Kubernetes Metrics Server](https://github.com/kubernetes-sigs/metrics-server).
+
+```bash
+$ kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.4.1/components.yaml
+```
+
+Lets' verify the status of the metrics-server APIService (it could take a few minutes).
+
+```bash
+$ kubectl get apiservice v1beta1.metrics.k8s.io -o json | jq '.status'
+
+
+{
+  "conditions": [
+    {
+      "lastTransitionTime": "2020-12-21T15:42:43Z",
+      "message": "all checks passed",
+      "reason": "Passed",
+      "status": "True",
+      "type": "Available"
+    }
+  ]
+}
+```
+
+**We are now ready to scale a deployed application**
+
+A new `addon` is set in our system we can check 
+
+## Deploy a Sample App
+
+We will deploy an application and expose as a service on TCP port 80.
+
+The application is a custom-built image based on the php-apache image. The index.php page performs calculations to generate CPU load. More information can be found [here](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/#run-expose-php-apache-server)
+
+```bash
+kubectl create deployment php-apache --image=us.gcr.io/k8s-artifacts-prod/hpa-example
+kubectl set resources deploy php-apache --requests=cpu=200m
+kubectl expose deploy php-apache --port 80
+
+kubectl get pod -l app=php-apache
+
+```
+
+## Create an HPA resource
+
+This HPA scales up when CPU exceeds 50% of the allocated container resource.
+
+```bash
+kubectl autoscale deployment php-apache `#The target average CPU utilization` \
+    --cpu-percent=50 \
+    --min=1 `#The lower limit for the number of pods that can be set by the autoscaler` \
+    --max=10 `#The upper limit for the number of pods that can be set by the autoscaler`
+
+```
+
+View the HPA using kubectl. You probably will see <unknown>/50% for 1-2 minutes and then you should be able to see 0%/50%
+
+```bash
+$ kubectl get hpa
+``` 
+
+## Generate load to trigger scaling
+
+**Open a new terminal**
+
+```bash
+$ kubectl --generator=run-pod/v1 run -i --tty load-generator --image=busybox /bin/sh
+
+```
+
+> Reference: https://medium.com/better-programming/kubernetes-tips-create-pods-with-imperative-commands-in-1-18-62ea6e1ceb32
+
+Execute a while loop to continue getting http://php-cache
+
+```bash
+while true; do wget -q -O - http://php-apache; done
+``` 
+
+In the previous tab, watch the HPA with the following command
+
+```bash
+$ kubectl get hpa -w
+
+```
+
+You can now stop (Ctrl + C) load test that was running in the other terminal. You will notice that HPA will slowly bring the replica count to min number based on its configuration. You should also get out of load testing application by pressing Ctrl + D.