docs: create comprehensive AGENTS.md file

Co-authored-by: leecalcote <7570704+leecalcote@users.noreply.github.com>

Author: Copilot

AGENTS.md

@@ -89,13 +89,13 @@ Workflow:
 git checkout -b feature/your-feature
 ```
 
-3. Commit changes:
+1. Commit changes:
 
 ```bash
 git commit -m "Describe your change"
 ```
 
-4. Push and open a Pull Request.
+1. Push and open a Pull Request.
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for more details.
 

README.md

@@ -16,7 +16,7 @@ weight: 5
 
 Note: The comment `//export go_filter` on function is required and it should be the same as the function name.
 
-3. Using the function parameters we will have access to the original log record, tag, and timestamp. Here is an example log record:
+1. Using the function parameters we will have access to the original log record, tag, and timestamp. Here is an example log record:
 
     ```bash
     {
@@ -25,17 +25,17 @@ Note: The comment `//export go_filter` on function is required and it should be
     }
     ```
 
-4. **Processing the record:**
+2. **Processing the record:**
 
     - The function parameter **record** is of type byte slice, which presumably contains a JSON string, and is converted to a Go string.
 
     - This string is then parsed using the **fastjson** package.
 
-5. **Determining the region:**
+3. **Determining the region:**
 
     - The **getRegion** function takes an IP address as a string, parses it, converts it to an integer, and determines which region the IP address belongs to based on predefined IP ranges. If the IP address is invalid or doesn’t fall within any range, an error is returned.
 
-6. **Modify and return:**
+4. **Modify and return:**
 
     - The determined region is added to the original JSON. The modified record will look like this:
 
@@ -52,6 +52,6 @@ Note: The comment `//export go_filter` on function is required and it should be
 
     - Note that there’s an explicit null terminator added to the end of the string before converting it back to a byte slice This is necessary for compatibility with whatever system reads this output, perhaps a C/C++ framework.
 
-7. The **main** function is empty because the primary function here **(go_filter)** is meant to be exported and used as a plugin.
+5. The **main** function is empty because the primary function here **(go_filter)** is meant to be exported and used as a plugin.
 
 Follow the [official documentation](https://docs.fluentbit.io/manual/development/wasm-filter-plugins) for more information on writing WASM plugins.

content/challenges/d011fd20-a3f5-4480-883b-dfb34321d168/processing-log-data-with-fluent-bit-and-wasm/program-explanation/_index.md

@@ -11,7 +11,6 @@ Issuers and ClusterIssuers are cert-manager resources that represent certificate
 
 We create a ClusterIssuer, a cluster-scoped resource used to configure a Certificate Authority (CA) - in this example, Let’s Encrypt. We configure it to use the HTTP-01 challenge method for domain validation and explicitly tell it to solve these challenges via the **calico-demo-gw** Gateway.
 
-
 Create a clusterissuer resource:
 
 ```bash

content/challenges/d011fd20-a3f5-4480-883b-dfb34321d168/securing-k8s-traffic-with-calico-ingress-gateway/content/clussterissuer/_index.md

@@ -19,6 +19,7 @@ Deploy the application; this pulls the Kubernetes manifests from the official Gi
 kubectl create -f 
 https://raw.githubusercontent.com/GoogleCloudPlatform/microservices-demo/refs/heads/release/v0.10.2/release/kubernetes-manifests.yaml
 ```
+
 Now that the application is deployed, we can verify the status of the frontend deployment and identify the associated ClusterIP service:
 
 ```bash
@@ -38,5 +39,5 @@ frontend                ClusterIP      10.100.42.132    <none>
 frontend-external       LoadBalancer   10.100.43.33     a78ef864683d543e59c7d91fba812176-247554297.us-west-2.elb.amazonaws.com   80:30816/TCP   5d19h
 ```
 
-At this point, our application is successfully deployed, and our customers can access it using the DNS name provided by the load balancer. However, this traffic is unencrypted, which highlights the key security gap we’re aiming to address. 
+At this point, our application is successfully deployed, and our customers can access it using the DNS name provided by the load balancer. However, this traffic is unencrypted, which highlights the key security gap we’re aiming to address.
 Next, we will use Calico Ingress Gateway to equip our application with SSL and run it over HTTPS without modifying our application or server code.

content/challenges/d011fd20-a3f5-4480-883b-dfb34321d168/securing-k8s-traffic-with-calico-ingress-gateway/content/deploy-a-demo/_index.md

@@ -20,7 +20,7 @@ metadata:
 EOF
 ```
 
-This Calico-specific Gateway API resource is the essential prerequisite for using Kubernetes Gateway API standard objects. 
+This Calico-specific Gateway API resource is the essential prerequisite for using Kubernetes Gateway API standard objects.
 
 Let's check the deployment status:
 

content/challenges/d011fd20-a3f5-4480-883b-dfb34321d168/securing-k8s-traffic-with-calico-ingress-gateway/content/enable-calico/_index.md

@@ -58,4 +58,4 @@ You should see an output similar to the following:
 NAME         AVAILABLE   PROGRESSING   DEGRADED   SINCE
 calico       True        False         False      4d10h
 ippools      True        False         False      4d10h
-```
+```

content/challenges/d011fd20-a3f5-4480-883b-dfb34321d168/securing-k8s-traffic-with-calico-ingress-gateway/content/install-calico/_index.md

@@ -25,4 +25,4 @@ This microcourse guides you through the settings and basic configurations requir
 
 #### What Makes Gateway API Different?
 
-There are three main points we should highlight when evaluating Gateway API and Ingress controllers.
+There are three main points we should highlight when evaluating Gateway API and Ingress controllers.

content/challenges/d011fd20-a3f5-4480-883b-dfb34321d168/securing-k8s-traffic-with-calico-ingress-gateway/content/overview/_index.md

@@ -9,4 +9,4 @@ weight: 3
 
 We need a running Kubernetes environment to deploy Calico, our application, and the Gateway API resources, which happens in this step. We used EKS for our example because we wanted to tie the Gateway API resources to an actual domain and a valid certificate to emphasize its application in a real-world scenario.
 
-Let's create an EKS cluster with the **eksctl** command:
+Let's create an EKS cluster with the **eksctl** command:

content/challenges/d011fd20-a3f5-4480-883b-dfb34321d168/securing-k8s-traffic-with-calico-ingress-gateway/content/spin-up-k8s/_index.md

@@ -20,47 +20,47 @@ $ docker run --name myjenkins1 -dit -p 8080:8080 -p 50000:50000 -v
 jenkins_data:/var/jenkins_home jenkins/jenkins:2.60.3-alpine
 ```
 
-2. List the container running the following command:
+1. List the container running the following command:
 
 ```bash
 docker container ls
 ```
 
-3. View the logs and capture the initial admin password for Jenkins by executing the following
+1. View the logs and capture the initial admin password for Jenkins by executing the following
 command:
 
 ```bash
 docker logs myjenkins1| grep -B 5 initialAdminPassword
 ```
 
-4. Access the Jenkins server and perform the initial configuration.
+1. Access the Jenkins server and perform the initial configuration.
 Open the browser and access the URL:<http://HostIP:8080> (curl ifconfig.io to
 get your public IP).
 
 ![Initial Jenkins Setup](step1.png)
 
-5. Enter the initial admin password and click on continue:
+1. Enter the initial admin password and click on continue:
 
 ![Initial Jenkins Setup](step2.png)
 
-6. Choose the “Select Plugins to install” option and click on “none”, then click on Install. The
+1. Choose the “Select Plugins to install” option and click on “none”, then click on Install. The
 initial installation does not contain any plugins by default. We can install plugins of our
 choice. However, to keep it simple, we will choose “none” in this lab and move forward.
 
 ![Initial Jenkins Setup](step3.png)
 
 !![Initial Jenkins Setup](step4.png)
 
-7. Admin user can be created during this step. We will skip the step and select “Continue as
+1. Admin user can be created during this step. We will skip the step and select “Continue as
 admin” and proceed to the next step.
 
 ![Initial Jenkins Setup](step5.png)
 
-8. Jenkins is set up and ready to use. Click on Start using Jenkins to proceed further.
+1. Jenkins is set up and ready to use. Click on Start using Jenkins to proceed further.
 
 ![Initial Jenkins Setup](step6.png)
 
-9. The initial admin password was generated during installation; reset the password of the
+1. The initial admin password was generated during installation; reset the password of the
 admin user and change it to one of your choice.
 
 ![Initial Jenkins Setup](step7.png)
@@ -69,44 +69,44 @@ Update the Password and confirm.
 
 ![Initial Jenkins Setup](step8.png)
 
-10. Now that Jenkins is ready, create a new job to test the working on Jenkins.
+1. Now that Jenkins is ready, create a new job to test the working on Jenkins.
 
 ![Initial Jenkins Setup](step9.png)
 
-11. Notice that there are no projects available; this is because we skipped installing additional
+1. Notice that there are no projects available; this is because we skipped installing additional
 plugins during the setup. We can add plugins later, for now we will make use of the default
 Freestyle Project plugin available and set up a test job to execute a command.
 
 ![Initial Jenkins Setup](step10.png)
 
-12. Under the Build section, select Execute shell to execute a command
+1. Under the Build section, select Execute shell to execute a command
 
 ![Initial Jenkins Setup](step11.png)
 
-13. Instead of creating a complex command, we are just executing a simple “ls” command. Type
+1. Instead of creating a complex command, we are just executing a simple “ls” command. Type
 “ls” in the command box, save and exit
 
 ![Initial Jenkins Setup](step12.png)
 
-14. On the Jenkins dashboard you will find the newly created Project test_job.
+1. On the Jenkins dashboard you will find the newly created Project test_job.
 
 ![Initial Jenkins Setup](step13.png)
 
-15. Click on Build Now on the left hand pane, to execute the command or to run the build
+1. Click on Build Now on the left hand pane, to execute the command or to run the build
 
 ![Initial Jenkins Setup](step14.png)
 
-16. The build job is completed in a few seconds; click on the build number in build history to
+1. The build job is completed in a few seconds; click on the build number in build history to
 view the console output, which displays the log output of the completed job.
 
 ![Initial Jenkins Setup](step15.png)
 
-17. Congratulations!!! You have successfully installed Jenkins, configured it, created and
+1. Congratulations!!! You have successfully installed Jenkins, configured it, created and
 executed a simple job on Jenkins.
 If you like, go ahead and explore the Jenkins Server by adding new plugins and creating
 pipelines.
 
-18. Clean up by logging off the Jenkins Server, then stop and remove the myjenkins
+2. Clean up by logging off the Jenkins Server, then stop and remove the myjenkins
 container, by executing the following commands.
 
 ```bash