GeoIP updates (#79)

* lab12 initial docs
* lab12 rough draft
* lab12 final draft
* typos
* fix nodeport
* appworld updates
* geoip updates

Author: chrisakker

labs/lab11/as.geo.example.com.conf

@@ -11,7 +11,7 @@ server {
 
     location / {
 
-        return 200 "Welcome to N4A Workshop, website $host\n";
+        return 200 "Welcome to N4A Workshop, Asia website at $host\n";
         add_header X-DCTEST-FQDN $host;
 
     }

labs/lab11/eu.geo.example.com.conf

@@ -11,7 +11,7 @@ server {
 
     location / {
 
-        return 200 "Welcome to N4A Workshop, website $host\n";
+        return 200 "Welcome to N4A Workshop, Europe website at $host\n";
         add_header X-DCTEST-FQDN $host;
 
     }

labs/lab11/media/lab11_3datacenters.png

@@ -1,4 +1,4 @@
-# Nginx 4 Azure - na.example.com.conf
+# Nginx 4 Azure - na.geo.example.com.conf
 # Chris Akker, Shouvik Dutta, Adam Currier - Jan 2025
 #
 # Nginx Server Block for GeoIP Continent Routing
@@ -11,7 +11,7 @@ server {
 
     location / {
 
-        return 200 "Welcome to N4A Workshop, website $host\n";
+        return 200 "Welcome to N4A Workshop, North America website at $host\n";
         add_header X-DCTEST-FQDN $host;
 
     }

labs/lab11/na.geo.example.com.conf

@@ -98,7 +98,7 @@ In your NGINX for Azure instance, the main NGINX `/etc/nginx/nginx.conf` file mu
 
     ```
 
-    Submit you NGINX Configuration, NGINX for Azure will validate it for you.  You must fix any errors before proceeding.
+    Submit your NGINX Configuration, NGINX for Azure will validate it for you.  You must fix any errors before proceeding.
 
 <br/>
 
@@ -213,7 +213,9 @@ NGINXaaS for Azure | Global Data Centers | GeoIP2
 
 <br/>
 
-As you are likely a DevOps Engineer, Application Architect/Developer, or NGINX Admin with Global responsibilities, you have `multiple Data Centers spread around the world or the country`.  As you also have users also around the world, you are probably using traditional `Global Server Load Balancing` and "SmartDNS" systems, to respond to DNS queries for your FQDNs.  However, these systems are not usually in your control, and there is likely an entirely different team responsible for DNS administration/management, right?  OH groan, more tickets and waiting...  **What if there was an easier way, to find a user's location, and route the users to the closest data center?**
+As you are likely a DevOps Engineer, Application Architect/Developer, or NGINX Admin with Global responsibilities, you have `multiple Data Centers spread around the world or the country`.  As you also have users also around the world, you are probably using traditional `Global Server Load Balancing` and "SmartDNS" systems, to respond to DNS queries for your FQDNs.  However, these systems are not usually in your control, and there is likely an entirely different team responsible for DNS administration/management, right?  OH groan, more tickets and waiting...  
+
+>**What if there was an easier way, to find a user's location, and route the users to the closest data center?**
 
 You can easily do that with NGINX and the MaxMind GeoIP2 module, without requiring many changes from your DNS admin team.
 
@@ -233,15 +235,19 @@ Reduce the cost of GSLB systems |
 
 <br/>
 
-But this Solution does eliminate or minimize many of the current challenges that exist with GSLB/DNS systems.  The two most common NGINX-DevOps headaches are:
+But this Solution *does* eliminate or minimize many of the current challenges that exist with GSLB/DNS systems.  The two most common NGINX-DevOps headaches are:
 
 - Lack of DNS Admin access/control 
 - *DNS caching of A records at multple points in the DNS system that you can't see or control, such as*:
     - Clients'/Browsers' local DNS Resolver cache 
     - Internet/Cloud provider's DNS servers' cache
     - Your Company's DNS SOA/Nameservers in the Data Centers
 
-In this exercise, you will route traffic to three Data Centers spread around the world, without using DNS.  One Data Center in North America, one in Europe, and one in Asia.  You will use the NGINX `$geoip2_data_continent_code variable` to redirect users to the Data Center in those three regions.  You will use the NGINX `map directive` to associate the MaxMind Continent Code to a 2-character identifier, as a DNS sub-domain, as shown here:
+In this exercise, you will route traffic to three Data Centers spread around the world, without using DNS.  One Data Center in North America, one in Europe, and one in Asia.  
+
+![N4A](media/lab11_3datacenters.png)
+
+You will use the NGINX `$geoip2_data_continent_code variable` to redirect users to the Data Center in those three regions.  You will use the NGINX `map directive` to associate the MaxMind Continent Code to a 2-character identifier, as a DNS sub-domain, as shown here:
 
 ```nginx
 map $geoip2_data_continent_code $nearest_data_center {  
@@ -304,7 +310,7 @@ map $geoip2_data_continent_code $nearest_data_center {
     Here are the three new files, just copy/paste:
 
     ```nginx
-    # NGINX 4 Azure - na.example.com.conf
+    # NGINX 4 Azure - na.geo.example.com.conf
     # Chris Akker, Shouvik Dutta, Adam Currier - Jan 2025
     # NGINX Server Block for GeoIP Continent Routing
     #

labs/lab11/readme.md

@@ -0,0 +1,23 @@
+apiVersion: v1
+kind: Service
+metadata:
+  name: nginx-ingress
+  namespace: nginx-ingress
+spec:
+  type: NodePort
+  ports:
+  - port: 80
+    nodePort: 32080
+    protocol: TCP
+    name: http
+  - port: 443
+    nodePort: 32443
+    protocol: TCP
+    name: https
+  - port: 9000
+    nodePort: 32090
+    protocol: TCP
+    name: dashboard    
+  selector:
+    app: nginx-ingress
+    

labs/lab12/nodeport-static.yaml

@@ -581,4 +581,4 @@ You can also see that the NLK Controller will track your Cluster Node Scaling ch
 
 -------------
 
-Navigate to [LabGuide](../readme.md)
+Navigate to [LabGuide](../readme.md)

labs/lab12/readme.md

@@ -14,7 +14,7 @@ spec:
     spec:
       containers:
       - name: coffee
-        image: nginxinc/ingress-demo
+        image: chrisakker/ingress-demo
         ports:
         - containerPort: 80
 ---
@@ -49,7 +49,7 @@ spec:
     spec:
       containers:
       - name: tea
-        image: nginxinc/ingress-demo
+        image: chrisakker/ingress-demo
         ports:
         - containerPort: 80
 ---

labs/lab4/cafe.yaml

@@ -0,0 +1,69 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: coffee
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app: coffee
+  template:
+    metadata:
+      labels:
+        app: coffee
+    spec:
+      containers:
+      - name: coffee
+        image: nginxinc/ingress-demo
+        ports:
+        - containerPort: 80
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: coffee-svc
+spec:
+  type: ClusterIP
+  clusterIP: None
+  ports:
+  - port: 80
+    targetPort: 80
+    protocol: TCP
+    name: http
+  selector:
+    app: coffee
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: tea
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app: tea
+  template:
+    metadata:
+      labels:
+        app: tea
+    spec:
+      containers:
+      - name: tea
+        image: nginxinc/ingress-demo
+        ports:
+        - containerPort: 80
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: tea-svc
+spec:
+  type: ClusterIP
+  clusterIP: None
+  ports:
+  - port: 80
+    targetPort: 80
+    protocol: TCP
+    name: http
+  selector:
+    app: tea