Merge pull request #67 from Lemoncode/aks-segunda-edicion

0GiS0 · web-flow · commit c8a5e8710f44 · 2022-01-11T17:26:48.000+01:00
Aks segunda edición
diff --git a/.gitignore b/.gitignore
@@ -30,3 +30,4 @@ app/
 .aws/
 lab/
 private.readme.md
+04-cloud/00-aks/03-virtual-kubelet/auth.json
diff --git a/04-cloud/00-aks/00-mi-primer-aks/.gitignore b/04-cloud/00-aks/00-mi-primer-aks/.gitignore
@@ -0,0 +1,37 @@
+# Local .terraform directories
+**/.terraform/*
+
+# .tfstate files
+*.tfstate
+*.tfstate.*
+
+# Crash log files
+crash.log
+crash.*.log
+
+# Exclude all .tfvars files, which are likely to contain sentitive data, such as
+# password, private keys, and other secrets. These should not be part of version
+# control as they are data points which are potentially sensitive and subject
+# to change depending on the environment.
+#
+*.tfvars
+
+# Ignore override files as they are usually used to override resources locally and so
+# are not checked in
+override.tf
+override.tf.json
+*_override.tf
+*_override.tf.json
+
+# Include override files you do wish to add to version control using negated pattern
+#
+# !example_override.tf
+
+# Include tfplan files to ignore the plan output of command: terraform plan -out=tfplan
+# example: *tfplan*
+
+# Ignore CLI configuration files
+.terraformrc
+terraform.rc
+
+.terraform.lock.hcl
diff --git a/04-cloud/00-aks/00-mi-primer-aks/00-crear-mi-primer-aks.sh b/04-cloud/00-aks/00-mi-primer-aks/00-crear-mi-primer-aks.sh
@@ -7,20 +7,24 @@ brew install azure-cli
 #También podemos crear un contenedor con Azure CLI. Así no tenemos que instalarlo en nuestro local ;-)
 docker run -it --rm microsoft/azure-cli sh
 
+# Para ver el subconjunto de serviios que puedes gestionar a través de la linea de comandos:
+az
+
 #Iniciamos sesión en nuestra cuenta de Azure
 az login
 
 #Creamos un grupo de recursos en una ubicación concreta
-RESOURCE_GROUP="Mi-Primer-AKS"
+RESOURCE_GROUP="Lemoncode-CLI"
 LOCATION="northeurope"
 
 az group create -n ${RESOURCE_GROUP} -l ${LOCATION}
 
 #Creamos el clúster de AKS
-AKS_NAME="lemoncode-aks"
+AKS_NAME="aks-lemoncode-cli"
 
 #https://docs.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az_aks_create
-az aks create -g ${RESOURCE_GROUP} -n ${AKS_NAME} \
+az aks create -g ${RESOURCE_GROUP} \
+-n ${AKS_NAME} \
 --node-count 1 --generate-ssh-keys
 
 #Instalamos kubectl en local si no lo tenemos. En este caso en el contenedor con Azure CLI
@@ -32,14 +36,17 @@ az aks get-credentials -g ${RESOURCE_GROUP} -n ${AKS_NAME}
 #Recuperamos los nodos de nuestro clúster (en este ejemplo solo deberíamos de tener 1)
 kubectl get nodes
 
-#Recuperamos todos los servicios desplegados en nuestro clúster
-kubectl get services --all-namespaces
-
 #Escalar el número de nodos en el clúster
 az aks scale -g ${RESOURCE_GROUP} -n ${AKS_NAME} --node-count 3
 
 #Ahora deberíamos tener 3 nodos en lugar de 1
 kubectl get nodes
 
+# Crear un Wordpress en nuestro clúster
+kubectl apply -f wordpress.yaml
+
+# Comprobar lo que acabamos de desplegar
+kubectl get all -n wordpress
+
 #Si eliminamos el grupo de recursos eliminaremos el clúster
 az group delete -n ${RESOURCE_GROUP} --yes --no-wait
diff --git a/04-cloud/00-aks/00-mi-primer-aks/main.tf b/04-cloud/00-aks/00-mi-primer-aks/main.tf
@@ -0,0 +1,26 @@
+provider "azurerm" {
+  features {}
+}
+
+resource "azurerm_resource_group" "rg" {
+  name     = "Lemoncode-Terraform"
+  location = "West Europe"
+}
+
+resource "azurerm_kubernetes_cluster" "k8s" {
+  name                = "aks-lemoncode-tf"
+  resource_group_name = azurerm_resource_group.rg.name
+  location            = azurerm_resource_group.rg.location
+  dns_prefix          = "aks-lemoncode-tf"
+
+  default_node_pool {
+    name       = "default"
+    node_count = 1
+    vm_size    = "Standard_DS2_v2"
+  }
+
+  identity {
+    type = "SystemAssigned"
+  }
+
+}
diff --git a/04-cloud/00-aks/00-mi-primer-aks/wordpress.yaml b/04-cloud/00-aks/00-mi-primer-aks/wordpress.yaml
@@ -0,0 +1,113 @@
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: wordpress
+
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: wordpress-mysql
+  namespace: wordpress
+  labels:
+    app: wordpress
+spec:
+  selector:
+    matchLabels:
+      app: wordpress
+      tier: mysql
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      labels:
+        app: wordpress
+        tier: mysql
+    spec:
+      containers:
+        - image: mysql:5.6
+          name: mysql
+          env:
+            - name: MYSQL_ROOT_PASSWORD
+              value: wp_password
+          ports:
+            - containerPort: 3306
+              name: mysql
+          volumeMounts:
+            - name: mysql-storage
+              mountPath: /var/lib/mysql
+      volumes:
+        - name: mysql-storage
+          emptyDir: {}
+
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: wordpress-mysql
+  namespace: wordpress
+  labels:
+    app: wordpress
+spec:
+  ports:
+    - port: 3306
+  selector:
+    app: wordpress
+    tier: mysql
+  clusterIP: None
+
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: wordpress
+  namespace: wordpress
+  labels:
+    app: wordpress
+spec:
+  selector:
+    matchLabels:
+      app: wordpress
+      tier: frontend
+  replicas: 2
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      labels:
+        app: wordpress
+        tier: frontend
+    spec:
+      containers:
+        - image: wordpress:4.8-apache
+          name: wordpress
+          env:
+            - name: WORDPRESS_DB_HOST
+              value: wordpress-mysql
+            - name: WORDPRESS_DB_PASSWORD
+              value: wp_password
+          ports:
+            - containerPort: 80
+              name: wordpress
+          volumeMounts:
+            - name: wordpress-storage
+              mountPath: /var/www/html
+      volumes:
+        - name: wordpress-storage
+          emptyDir: {}
+
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: wordpress
+  namespace: wordpress
+  labels:
+    app: wordpress
+spec:
+  ports:
+    - port: 80
+  selector:
+    app: wordpress
+    tier: frontend
+  type: LoadBalancer
diff --git a/04-cloud/00-aks/02-cluster-autoscaler/cluster-autoscaler.sh b/04-cloud/00-aks/02-cluster-autoscaler/cluster-autoscaler.sh
@@ -1,4 +1,3 @@
-
 # Variables
 RESOURCE_GROUP="Cluster-Autoscaler"
 AKS_NAME="lemoncode-autoscaler"
@@ -8,8 +7,10 @@ LOCATION="northeurope"
 az group create -n ${RESOURCE_GROUP} -l ${LOCATION}
 
 #Crear cluster de AKS
-az aks create -g ${RESOURCE_GROUP} -n ${AKS_NAME} \
---node-count 1 --generate-ssh-keys
+az aks create -g ${RESOURCE_GROUP} \
+-n ${AKS_NAME} \
+--node-count 1 \
+--generate-ssh-keys
 
 # Recuperar el contexto para este clúster
 az aks get-credentials -n $AKS_NAME -g $RESOURCE_GROUP
@@ -30,7 +31,7 @@ az aks update \
   --name $AKS_NAME \
   --enable-cluster-autoscaler \
   --min-count 1 \
-  --max-count 3
+  --max-count 5
 
 #Mientras esto se materializa puedes ver en el portal de Azure que el virtual machine scaleset está aumentando
 #el número de instancias. Este proceso puede llevar varios minutos ya que tiene que dar de alta las VMs
diff --git a/04-cloud/00-aks/03-virtual-kubelet/02-virtual-kubelet.sh b/04-cloud/00-aks/03-virtual-kubelet/02-virtual-kubelet.sh
@@ -36,13 +36,13 @@ az network vnet subnet create \
     --address-prefixes 192.168.2.0/24
 
 #Crear un service principal
-az ad sp create-for-rbac --skip-assignment
-SP_ID="a53cffe7-cb13-40d5-aefd-e36c5569869c"
-SP_PASSWORD="qqbZ0z3l2Zac104_wvh0HBj_-KyTzFeVO~"
+az ad sp create-for-rbac --name kubelet-demo > auth.json
+CLIENT_ID=$(jq -r '.appId' auth.json)
+PASSWORD=$(jq -r '.password' auth.json)
 
 #Asignamos permisos a la red virtual para que el cluster pueda gestionarla
 VNET_ID=$(az network vnet show --resource-group $RESOURCE_GROUP --name $AKS_VNET --query id -o tsv)
-az role assignment create --assignee $SP_ID --scope $VNET_ID --role Contributor
+az role assignment create --assignee $CLIENT_ID --scope $VNET_ID --role Contributor
 
 #Obtenemos el ID de la subnet donde va a ir el cluster de AKS
 SUBNET_ID=$(az network vnet subnet show --resource-group $RESOURCE_GROUP --vnet-name $AKS_VNET --name $AKS_SUBNET --query id -o tsv)
@@ -53,12 +53,9 @@ az aks create \
     --name $AKS_NAME \
     --node-count 1 \
     --network-plugin azure \
-    --service-cidr 10.0.0.0/16 \
-    --dns-service-ip 10.0.0.10 \
-    --docker-bridge-address 172.17.0.1/16 \
     --vnet-subnet-id $SUBNET_ID \
-    --service-principal $SP_ID \
-    --client-secret $SP_PASSWORD
+    --service-principal $CLIENT_ID \
+    --client-secret $PASSWORD
 
 # Recuperar el contexto para este clúster
 az aks get-credentials -n $AKS_NAME -g $RESOURCE_GROUP
diff --git a/04-cloud/00-aks/03-virtual-kubelet/manifests/nginx-deployment.yml b/04-cloud/00-aks/03-virtual-kubelet/manifests/nginx-deployment.yml
@@ -5,7 +5,7 @@ metadata:
   labels:
     app: nginx
 spec:
-  replicas: 3
+  replicas: 20
   selector:
     matchLabels:
       app: nginx
diff --git a/04-cloud/00-aks/04-keda/03-keda.sh b/04-cloud/00-aks/04-keda/03-keda.sh
@@ -1,3 +1,22 @@
+#KEDA
+# https://www.returngis.net/2020/06/autoescalar-tus-aplicaciones-en-kubernetes-con-keda/
+
+#Variables
+RESOURCE_GROUP="KEDA"
+AKS_NAME="lemoncode-keda"
+
+#Creamos el grupo de recursos
+az group create -n ${RESOURCE_GROUP} -l ${LOCATION}
+
+#Creamos un cluster
+az aks create -g ${RESOURCE_GROUP} \
+-n ${AKS_NAME} \
+--node-count 1 \
+--generate-ssh-keys
+
+#Configuramos kubectl para comunicarnos con nuestro nuevo clúster
+az aks get-credentials -g ${RESOURCE_GROUP} -n ${AKS_NAME}
+
 #Para entender KEDA primero necesitas saber cómo autoescalan los pods dentro de un clúster
 
 ### Ejemplo de autoescalado sin KEDA
@@ -6,34 +25,17 @@ kubectl apply -f 04-cloud/00-aks/04-keda/manifests/autoscale-with-hpa.yml
 kubectl autoscale deployment web --cpu-percent=30 --min=1 --max=5
 kubectl get hpa --watch
 
-ab -n 50000 -c 200 http://51.104.177.27/
+ab -n 50000 -c 200 http://20.82.253.97/
 
 kubectl describe hpa web
 
-#KEDA
-# https://www.returngis.net/2020/06/autoescalar-tus-aplicaciones-en-kubernetes-con-keda/
-
-#Variables
-RESOURCE_GROUP="KEDA"
-AKS_NAME="lemoncode-keda"
-
 #Instalar Helm
 brew install helm
 
 #Añadir el repo de KEDA
 helm repo add kedacore https://kedacore.github.io/charts
 helm repo update
 
-#Creamos el grupo de recursos
-az group create -n ${RESOURCE_GROUP} -l ${LOCATION}
-
-#Creamos un cluster
-az aks create -g ${RESOURCE_GROUP} -n ${AKS_NAME} \
---node-count 1 --generate-ssh-keys
-
-#Configuramos kubectl para comunicarnos con nuestro nuevo clúster
-az aks get-credentials -g ${RESOURCE_GROUP} -n ${AKS_NAME}
-
 #Creamos un namespace llamado keda
 kubectl create namespace keda
 
@@ -47,7 +49,7 @@ kubectl get pods -n keda --watch
 #Para ello nos apoyamos en un servicio llamado Azure Storage
 
 #Creamos una cuenta de almacenamiento
-STORAGE_NAME="boxoftasks"
+STORAGE_NAME="lemonboxoftasks"
 az storage account create --name $STORAGE_NAME --resource-group $RESOURCE_GROUP
 ACCOUNT_KEY=$(az storage account keys list --resource-group $RESOURCE_GROUP --account-name $STORAGE_NAME --query "[0].value" --output tsv)
 
diff --git a/04-cloud/00-aks/05-azure-active-directory/azure-ad-aks.sh b/04-cloud/00-aks/05-azure-active-directory/azure-ad-aks.sh
@@ -57,7 +57,7 @@ az aks get-credentials --resource-group $RESOURCE_GROUP --name $AKS_NAME --overw
 
 #Vamos a probar the north remembers creando un pod dentro de este namespace
 #Lanzar este comando te pedirá autenticación
-kubectl run --generator=run-pod/v1 nginx-north --image=nginx --namespace the-north-remembers
+kubectl run nginx-north --image=nginx --namespace the-north-remembers
 kubectl get po -n the-north-remembers
 
 #Si intentamos acceder al namespace de los Lanister o el default nos dará error
@@ -69,7 +69,7 @@ kubectl get po
 az aks get-credentials --resource-group $RESOURCE_GROUP --name $AKS_NAME --overwrite-existing
 
 #Intentamos la misma operación pero en el namespace de los Lanister
-kubectl run --generator=run-pod/v1 nginx-kings-landing --image=nginx --namespace kings-landing
+kubectl run nginx-kings-landing --image=nginx --namespace kings-landing
 #Si intentamos entrar en The North Remembers da un error
 kubectl get po -n the-north-remembers
 
diff --git a/04-cloud/00-aks/05-azure-active-directory/manifests/kings-landing.yaml b/04-cloud/00-aks/05-azure-active-directory/manifests/kings-landing.yaml
diff --git a/04-cloud/00-aks/05-azure-active-directory/manifests/the-north-remembers.yaml b/04-cloud/00-aks/05-azure-active-directory/manifests/the-north-remembers.yaml
