Merge branch 'master' into resources

Signed-off-by: Lee Calcote <[email protected]>

Author: leecalcote

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

@@ -15,5 +15,14 @@ prerequisite_knowledge:
       - title: "Self-hosted Meshery"
         link: "https://docs.meshery.io/installation"
       - title: "Meshery Playground"
-        link: "https://play.meshery.io"        
+        link: "https://play.meshery.io"
+        
+additional_attributes:
+  - title: "Retake Policy"
+    value: "3"
+    description: "Up to three retakes allowed per exam"
+  - title: "Scoring"
+    value: "Composite"
+    description: "The certification requires passing the exam with a minimum passing score for recertification tracking."
+
 ---

content/challenges/d011fd20-a3f5-4480-883b-dfb34321d168/cncf-auto-scaling-challenge/_index.md

@@ -16,5 +16,14 @@ prerequisite_knowledge:
       - title: "Self-hosted Meshery"
         link: "https://docs.meshery.io/installation"
       - title: "Meshery Playground"
-        link: "https://play.meshery.io"       
+        link: "https://play.meshery.io"
+        
+additional_attributes:
+  - title: "Retake Policy"
+    value: "3"
+    description: "Up to three retakes allowed per exam"
+  - title: "Scoring"
+    value: "Composite"
+    description: "The certification requires passing the exam with a minimum passing score for recertification tracking."
+
 ---

content/challenges/d011fd20-a3f5-4480-883b-dfb34321d168/cncf-observability-challenge-with/_index.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.