reviewed ingress demos

Author: JaimeSalas

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

@@ -13,7 +13,6 @@ 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.
@@ -24,6 +23,9 @@ 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
@@ -34,9 +36,22 @@ With this we can explore kube-ops-view output by checking the details about the
 
 ```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.
 
-> Reference: https://kubernetes-operational-view.readthedocs.io/en/latest/
+> Reference: https://kubernetes-operational-view.readthedocs.io/en/latest/
+
+## Alternative installation
+
+```bash
+helm repo add christianknell https://christianknell.github.io/helm-charts
+helm repo update
+```
+
+```bash
+helm install kube-ops-view \
+ christianknell/kube-ops-view \
+ --set service.type=LoadBalancer
+```
+

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

@@ -11,15 +11,18 @@ 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
+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'
+kubectl get apiservice v1beta1.metrics.k8s.io -o json | jq '.status'
+```
 
+We expect an output similar to this:
 
+```json
 {
   "conditions": [
     {
@@ -35,7 +38,12 @@ $ kubectl get apiservice v1beta1.metrics.k8s.io -o json | jq '.status'
 
 **We are now ready to scale a deployed application**
 
-A new `addon` is set in our system we can check 
+A new `addon` is set in our system we can check by running:
+
+```bash
+kubectl get pods -n kube-system
+```
+
 
 ## Deploy a Sample App
 
@@ -67,7 +75,7 @@ kubectl autoscale deployment php-apache `#The target average CPU utilization` \
 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
+kubectl get hpa
 ``` 
 
 ## Generate load to trigger scaling
@@ -93,7 +101,7 @@ 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
+kubectl get hpa -w
 
 ```
 

04-cloud/01-eks/06-autoscalling-our-applications/02-cluster-auto-scaler/00-configure-cluster-autoscaler.md

@@ -16,10 +16,15 @@ Cluster Autoscaler will attempt to determine the CPU, memory, and GPU resources
 You configure the size of your Auto Scaling group by setting the minimum, maximum, and desired capacity. When we created the cluster we set these settings to 3.
 
 ```bash
-$ aws autoscaling \
+aws autoscaling \
     describe-auto-scaling-groups \
     --query "AutoScalingGroups[? Tags[? (Key=='eks:cluster-name') && Value=='lc-cluster']].[AutoScalingGroupName, MinSize, MaxSize,DesiredCapacity]" \
     --output table
+```
+
+We get  the following output:
+
+```
 -------------------------------------------------------------
 |                 DescribeAutoScalingGroups                 |
 +-------------------------------------------+----+----+-----+
@@ -46,10 +51,15 @@ aws autoscaling \
 
 ```bash
 # Check new values
-$ aws autoscaling \
+aws autoscaling \
     describe-auto-scaling-groups \
     --query "AutoScalingGroups[? Tags[? (Key=='eks:cluster-name') && Value=='lc-cluster']].[AutoScalingGroupName, MinSize, MaxSize,DesiredCapacity]" \
     --output table
+```
+
+We must see the updated values similar to this:
+
+```
 -------------------------------------------------------------
 |                 DescribeAutoScalingGroups                 |
 +-------------------------------------------+----+----+-----+

04-cloud/01-eks/07-exposing-service/fruits.ingress.yml

@@ -2,48 +2,24 @@ apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: example-ingress
+  annotations:
+    kubernetes.io/ingress.class: "nginx"
 spec:
   rules:
-    - host: jaimesalas.com
-      http:
-        paths:
-          - backend:
-              service:
-                name: apple-service
-                port:
-                  number: 5678
-            path: /apple
-            pathType: Prefix
-          - backend:
-              service:
-                name: banana-service
-                port:
-                  number: 5678
-            path: /banana
-            pathType: Prefix
-# apiVersion: extensions/v1beta1
-# kind: Ingress
-# metadata:
-#   name: example-ingress
-#   # annotations:
-# #    ingress.kubernetes.io/rewrite-target: /
-# # nginx.ingress.kubernetes.io/ssl-redirect: "false"
-# # nginx.ingress.kubernetes.io/force-ssl-redirect: "false"
-# # nginx.ingress.kubernetes.io/rewrite-target: /
-# spec:
-#   # tls:
-#   # - hosts:
-#   #   - anthonycornell.com
-#   #   secretName: tls-secret
-#   rules:
-#     - host: jaimesalas.com
-#       http:
-#         paths:
-#           - path: /apple
-#             backend:
-#               serviceName: apple-service
-#               servicePort: 5678
-#           - path: /banana
-#             backend:
-#               serviceName: banana-service
-#               servicePort: 5678
+  - host: "jaimesalas.com"
+    http:
+      paths:
+      - pathType: Prefix
+        path: "/apple"
+        backend:
+          service:
+            name: apple-service
+            port:
+              number: 5678
+      - pathType: Prefix
+        path: "/banana"
+        backend:
+          service:
+            name: banana-service
+            port:
+              number: 5678

04-cloud/01-eks/07-exposing-service/readme.md

@@ -101,45 +101,62 @@ spec:
 Create some services
 
 ```bash
-$ kubectl apply -f ./apple.deploy.yaml 
-$ kubectl apply -f ./banana.deploy.yaml
+kubectl apply -f ./apple.deploy.yaml 
+```
+
+```bash
+kubectl apply -f ./banana.deploy.yaml
 ``` 
 
 ## Step 2. Defining the Ingress resource to route traffic to the services created above
 
 Now declare an Ingress to route requests to `/apple` to the first service, and requests to `/banana` to second service. Create `fruits.ingress.yml`
 
 ```yml
-apiVersion: extensions/v1beta1
+apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: example-ingress
+  annotations:
+    kubernetes.io/ingress.class: "nginx"
 spec:
   rules:
-    - host: jaimesalas.com
-      http:
-        paths:
-          - path: /apple
-            backend:
-              serviceName: apple-service
-              servicePort: 5678
-          - path: /banana
-            backend:
-              serviceName: banana-service
-              servicePort: 5678
-
+  - host: "jaimesalas.com"
+    http:
+      paths:
+      - pathType: Prefix
+        path: "/apple"
+        backend:
+          service:
+            name: apple-service
+            port:
+              number: 5678
+      - pathType: Prefix
+        path: "/banana"
+        backend:
+          service:
+            name: banana-service
+            port:
+              number: 5678
 ```
 
+Note that we're using an annotation for `ingress.class`, since it's not set as the default one, we have to use the `annotation`. You can check this [link](https://stackoverflow.com/questions/65289827/nginx-ingress-controller-not-working-on-amazon-eks) on stackoverflow.
+
 And apply to our cluster
 
 ```bash
-$ kubectl apply -f fruits.ingress.yml
+kubectl apply -f fruits.ingress.yml
 ```
 
 Now to check that our ingress is working we need the `dns` of NLB that we have created, the easiest way to do this is run:
 
 ```bash
-$ kubectl get ingress
+kubectl get ingress
+```
+
+We get something simiar to this:
+
+```
 NAME              CLASS    HOSTS            ADDRESS                                                                         PORTS   AGE
 example-ingress   <none>   jaimesalas.com   a2e47070555144b06a0cd99a242d6753-ef17945a5e983c95.elb.eu-west-3.amazonaws.com   80      39m
 ```
@@ -148,7 +165,7 @@ The above adress is the `NLB` resource that's forwarding traffic to the ingress
 **-I** the response only contains the headers
 
 ```bash
-$ curl -I  http://a2e47070555144b06a0cd99a242d6753-ef17945a5e983c95.elb.eu-west-3.amazonaws.com
+curl -I  http://a2e47070555144b06a0cd99a242d6753-ef17945a5e983c95.elb.eu-west-3.amazonaws.com
 ```
 
 We get the following response
@@ -167,7 +184,7 @@ Connection: keep-alive
 Beacuse the **host** field is configured for the Ingress object, you must supply the **Host** header of the request with the same `hostname`
 
 ```bash
-$ curl -I -H "Host: jaimesalas.com" http://a2e47070555144b06a0cd99a242d6753-ef17945a5e983c95.elb.eu-west-3.amazonaws.com/apple/
+curl -I -H "Host: jaimesalas.com" http://a2e47070555144b06a0cd99a242d6753-ef17945a5e983c95.elb.eu-west-3.amazonaws.com/apple/
 ``` 
 
 And now we get the following result
@@ -188,14 +205,14 @@ X-App-Version: 0.2.3
 Deelete Ingress resource
 
 ```bash
-$ kubectl delete -f fruits.ingress.yml
+kubectl delete -f fruits.ingress.yml
 ``` 
 
 Delete services
 
 ```bash
-$ kubectl delete -f ./apple.deploy.yaml 
-$ kubectl delete -f ./banana.deploy.yaml
+kubectl delete -f ./apple.deploy.yaml 
+kubectl delete -f ./banana.deploy.yaml
 ```
 
 Delete NGINX Ingress Controller and NLB