Merge pull request #36 from Namanv0509/html-warning

Namanv0509 · web-flow · commit 130a4ab9a2b6 · 2025-07-26T18:57:27.000+05:30
Removing HTML tags
diff --git a/content/challenges/11111111-1111-1111-1111-111111111111/cncf-observability-challenge-with/distributed-tracing-with-jaeger/content/getting-started.md b/content/challenges/11111111-1111-1111-1111-111111111111/cncf-observability-challenge-with/distributed-tracing-with-jaeger/content/getting-started.md
@@ -25,6 +25,6 @@ Participants are ranked by score. Your score is determined by the number of test
 
 ### Can I participate in a sample challenge?
 
-Yes, we recommend that you participate in our <a> sample challenge </a>.
+Yes, we recommend that you participate in our sample challenge .
 
 This challenge enables you to understand how to participate in challenges on Meshery. It comprises detailed information about how questions should be attempted and details about the Meshery judge.
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-kubernetes-for-engineers/explore-dapr-with-meshery/dapr/conclusion/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-kubernetes-for-engineers/explore-dapr-with-meshery/dapr/conclusion/_index.md
@@ -9,7 +9,7 @@ weight: 7
 
 Congratulations! You have reached the end of this course on understanding how Dapr works in a Kubernetes cluster, using Meshery as a visual guide. Throughout this course, you learned how to import Dapr, Redis, and application configuration files into Meshery and visualize the resources and their relationships.
 
-You successfully created and configured a Dapr state store component using Meshery. You deployed the designs and visualized the deployed resources in the cluster using Operator mode. Additionally, you viewed the Dapr sidecars and observed the resources deployed in the <code>dapr-system</code> and <code>default</code> namespaces.
+You successfully created and configured a Dapr state store component using Meshery. You deployed the designs and visualized the deployed resources in the cluster using Operator mode. Additionally, you viewed the Dapr sidecars and observed the resources deployed in the `dapr-system` and `default` namespaces.
 
 Finally, you streamed the logs and observed the API calls, gaining a deeper understanding of how Dapr's APIs, such as the state management API and service invocation API, work together to facilitate seamless inter-service communication and efficient management of application state.
 
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-meshery/introduction-to-meshery/reviewing-designs/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-meshery/introduction-to-meshery/reviewing-designs/_index.md
@@ -42,7 +42,7 @@ You can add comments in two convenient ways:
 
 ![commenting-via-menu](commenting-via-menu.png)
 
-#### <u>Tips for using Comments as a Design Review Tool</u>
+#### Tips for using Comments as a Design Review Tool
 
 ![comments-as-design-tool](comments-as-design-tool.png)
 
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/conclusion/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/conclusion/_index.md
@@ -9,12 +9,12 @@ weight: 8
 id: "conclusion"
 ---
 
-{{< chapterstyle >}}
 
-<br />
+
+
 
 ### Congratulations!
 
 ##### You have successfully completed the course on **"Advanced concepts of service meshes - Hands on"** using _Istio_.
 
-{{< /chapterstyle >}}
+
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/deploy-an-application/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/deploy-an-application/_index.md
@@ -8,7 +8,7 @@ weight: 2
 title: "Deploy a sample application"
 ---
 
-{{< chapterstyle >}}
+
 
 To play with Istio and demonstrate some of it's capabilities, you will deploy the example BookInfo application, which is included the Istio package.
 
@@ -41,9 +41,9 @@ If your environment **does NOT** supports either of these two APIs, then you may
 
 As part of Istio deployment in [Previous chapter](./getting-started), you have deployed the sidecar injector.
 
-<h2 class="chapter-sub-heading">
-  <a name="auto"></a> Deploying Sample App with Automatic sidecar injection
-</h2>
+
+### Deploying Sample App with Automatic sidecar injection
+
 
 Istio, deployed as part of this workshop, will also deploy the sidecar injector. Let us now
 verify sidecar injector deployment.
@@ -148,14 +148,12 @@ kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml
 kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml
 ```
 
-<hr />
 
-<h3>
-  <a name="manual-sidecar-inj" />
-  Manual Sidecar Injection
-</h3>
 
-<p>Use this only when Automatic Sidecar injection doesn't work</p>
+### Manual Sidecar Injection
+
+
+Use this only when Automatic Sidecar injection doesn't work>
 
 To do a manual sidecar injection we will be using `istioctl` command:
 
@@ -185,4 +183,4 @@ kubectl apply -f <(curl https://raw.githubusercontent.com/istio/istio/master/sam
 
 Now continue to [Verify Bookinfo deployment](#verify).
 
-{{< /chapterstyle >}}
+
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/expose-services/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/expose-services/_index.md
@@ -8,7 +8,7 @@ title: "Expose services through Istio Ingress Gateway"
 id: "expose-services"
 ---
 
-{{< chapterstyle >}}
+
 The components deployed on the service mesh by default are not exposed outside the cluster. An Ingress Gateway is deployed as a Kubernetes service of type LoadBalancer (or NodePort). To make Bookinfo accessible external to the cluster, you have to create an `Istio Gateway` for the Bookinfo application and also define an `Istio VirtualService` with the routes we need.
 
 ### Inspecting the Istio Ingress Gateway
@@ -238,4 +238,3 @@ We can create a virtualservice & gateway for bookinfo app in the ingress gateway
 kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml
 ```
 
-{{< /chapterstyle >}}
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/getting-started/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/getting-started/_index.md
@@ -8,7 +8,7 @@ weight: 1
 title: "Getting Started with Istio"
 ---
 
-{{< chapterstyle >}}
+
 
 ### Setup Istio
 
@@ -105,4 +105,4 @@ Istio is deployed in a separate Kubernetes namespace `istio-system`. To check if
 kubectl get all -n istio-system
 ```
 
-{{< /chapterstyle >}}
+
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/observability/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/observability/_index.md
@@ -8,7 +8,7 @@ id: "observability"
 title: "Observability with Istio"
 ---
 
-{{< chapterstyle >}}
+
 
 ### Install Telemetry Add-ons
 
@@ -169,7 +169,7 @@ To do this the application collects and propagates the following headers from th
 
 Istio add-on services are deployed by default as `ClusterIP` type services. We can expose the services outside the cluster by either changing the Kubernetes service type to `NodePort` or `LoadBalancer` or by port-forwarding or by configuring Kubernetes Ingress. In this lab, we will briefly demonstrate the `NodePort` and port-forwarding ways of exposing services.
 
-<h5 class="chapter-alt-heading"> Option 1: Expose services with NodePort</h5>
+##### Option 1: Expose services with NodePort
 
 To expose them using NodePort service type, we can edit the services and change the service type from `ClusterIP` to `NodePort`
 
@@ -207,4 +207,4 @@ kubectl -n istio-system get svc tracing
 
 You can click on the link at the top of the page which maps to the right port and it will open Jaeger UI in a new tab.
 
-{{< /chapterstyle >}}
+
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/service-security-capabilities/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/service-security-capabilities/_index.md
@@ -8,7 +8,7 @@ id: "service-security-capabilities"
 title: "Service Security Capabilities of Istio"
 ---
 
-{{< chapterstyle >}}
+
 
 ### Access Control
 
@@ -272,4 +272,3 @@ spec:
   #     mode: DISABLE
 ```
 
-{{< /chapterstyle >}}
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/webassembly-and-intelligent-data-planes/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/advance-concepts-of-service-meshes/webassembly-and-intelligent-data-planes/_index.md
@@ -9,7 +9,7 @@ id: "webassembly-and-intelligent-data-planes"
 title: "WebAssembly and Intelligent Data Planes"
 ---
 
-{{< chapterstyle >}}
+
 
 In this lab, you will use the sample application [Image Hub](https://github.com/layer5io/image-hub). This version of the Image Hub filter has been simplified for your lab. To self-study deeper functionality, try the other version of the Image Hub filter that is available in the Image Hub repo.
 
@@ -22,8 +22,8 @@ In the Istio management page:
 1. Type default into the namespace field.
 2. Click the (+) icon on the Manage Sample Application Lifecycle card and select Image Hub Application to install the latest version of Image Hub
 
-<br />
-<br />
+
+
 
 ### Load the filter
 
@@ -36,11 +36,11 @@ In the Istio management page:
 1. Type default into the namespace field.
 2. Click the (+) icon on the Apply Service Mesh Configuration card and select Envoy Filter for Image Hub to deploy the custom filter.
 
-<br />
-<br />
+
+
 ## Send traffic
-<br />
-## Analyze behavior
+
+### Analyze behavior
 
 Alternative, manual installation steps are provided for reference below. No need to execute these if you have performed the steps above.
 
@@ -137,4 +137,4 @@ Manually patch the Image Hub Deployment.
 
 A future version of Meshery will allow you to deploy any filter from the [wasm-filters](https://github.com/layer5io/wasm-filters) repo. PR the repo to upload your custom filter and have Meshery deploy it.
 
-{{< /chapterstyle >}}
+
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/circuit-breaking/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/circuit-breaking/_index.md
@@ -7,20 +7,20 @@ title: "Circuit Breaking"
 weight: 8
 ---
 
-{{< chapterstyle >}}
+
 
 In this chapter we will configure circuit breaking using Istio. Circuit breaking allows developers to write applications that limit the impact of failures, latency spikes, and other undesirable effects of network peculiarities. This task will show how to configure circuit breaking for connections, requests, and outlier detection.
 
 ### Preparing for circuit breaking
-<br />
+
 
 Before we can configure circuit breaking, please try to access the `product page` app from within `Meshery` to ensure all the calls are making it through **without** errors as we did in [Observability chapter](observability)
 
 ![invalid-kubeconfig](meshery_initial_load_test.webp)
 
 ### Configure circuit breaking
 
-<br />
+
 Now that we have the needed services in place, it is time to configure circuit breaking using
 a destination rule.
 
@@ -70,7 +70,7 @@ spec:
 
 ### Time to trip the circuit
 
-<br />
+
 In the circuit-breaker settings, we specified maxRequestsPerConnection: 1 and http1MaxPendingRequests:
 1. This should mean that if we exceed more than one request per connection and more than one
 pending request, we should see the istio-proxy sidecar open the circuit for further requests/connections.
@@ -85,7 +85,7 @@ This will run the load test and show the results in a chart.
 
 You should only see a percentage of the requests succeed and the rest trapped by the configured circuit breaker.
 
-<br />
+
 
 ### Manual Steps
 
@@ -120,4 +120,4 @@ spec:
 EOF
 ```
 
-{{< /chapterstyle >}}
+
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/conclusion/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/conclusion/_index.md
@@ -7,12 +7,12 @@ lectures: 12
 weight: 9
 ---
 
-{{< chapterstyle >}}
 
-<br />
+
+
 
 ### Congratulations!
 
   You have successfully completed the course on **"Introduction to service meshes - Hands on"** using **Istio**.
 
-{{< /chapterstyle >}}
+
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/deploy-an-application/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/deploy-an-application/_index.md
@@ -7,12 +7,12 @@ lectures: 12
 weight: 2
 ---
 
-{{< chapterstyle >}}
+
 
 To play with Istio and demonstrate some of it's capabilities, you will deploy the example BookInfo application, which is included the Istio package.
 
 ### What is the Bookinfo Application
-<br />
+
 This application is a polyglot composition of microservices are written in different
 languages and sample BookInfo application displays information about a book, similar to a
 single catalog entry of an online book store. Displayed on the page is a description of
@@ -22,7 +22,7 @@ The end-to-end architecture of the application is shown in the figure.
 
 ![book-info](bookinfo-off-mesh.webp)
 
-<br />
+
 It’s worth noting that these services have no dependencies on Istio, but make an interesting
 service mesh example, particularly because of the multitude of services, languages and versions
 for the reviews service.
@@ -31,7 +31,7 @@ As shown in the figure below, proxies are sidecarred to each of the application
 
 ![book-info-on-mesh](bookinfo-on-mesh.webp)
 
-<br />
+
 Sidecars proxy can be either manually or automatically injected into the pods. Automatic sidecar
 injection requires that your Kubernetes api-server supports `admissionregistration.k8s.io/v1`
 or `admissionregistration.k8s.io/v1beta1` or `admissionregistration.k8s.io/v1beta2` APIs. Verify
@@ -45,10 +45,10 @@ If your environment **does NOT** supports either of these two APIs, then you may
 
 As part of Istio deployment in [Previous chapter](./getting-started), you have deployed the sidecar injector.
 
-<br />
+
 ### Deploying Sample App with Automatic sidecar injection
 
-<br />
+
 Istio, deployed as part of this workshop, will also deploy the sidecar injector. Let us now
 verify sidecar injector deployment.
 
@@ -90,9 +90,8 @@ This will do 3 things:
 1. Deploys all the BookInfo services in the `default` namespace.
 1. Deploys the virtual service and gateway needed to expose the BookInfo's productpage application in the `default` namespace.
 
-<h3 class="chapter-sub-heading">
-  <a name="verify"></a> Verify Bookinfo deployment{" "}
-</h3>
+#### Verify Bookinfo deployment
+
 
 1. Verify that the deployments are all in a state of AVAILABLE before continuing.
 
@@ -116,11 +115,11 @@ kubectl describe svc productpage
 
 Next, you will expose the BookInfo application to be accessed external from the cluster.
 
-<br />
+
 #### Alternative: Manual installation
 Follow this if the above steps did not work for you
-<br />
-<br />
+
+
 
 ##### Label namespace for injection
 
@@ -145,7 +144,7 @@ kube-system    Active    1h
 ```
 
 ##### Deploy BookInfo
-<br />
+
 
 Applying this yaml file included in the Istio package you collected in [Getting Started](./getting-started) will deploy the BookInfo app in you cluster.
 
@@ -159,8 +158,8 @@ kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml
 kubectl apply -f samples/bookinfo/networking/bookinfo-gateway.yaml
 ```
 
-<hr />
-<br />
+
+
 
 #### Manual Sidecar Injection
 
@@ -194,4 +193,3 @@ kubectl apply -f <(curl https://raw.githubusercontent.com/istio/istio/master/sam
 
 Now continue to [Verify Bookinfo deployment](#verify).
 
-{{< /chapterstyle >}}
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/expose-services/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/expose-services/_index.md
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/fault-injection/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/fault-injection/_index.md
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/getting-started/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/getting-started/_index.md
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/mutual-tls/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/mutual-tls/_index.md
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/observability/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/observability/_index.md
diff --git a/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/routing-and-canary/_index.md b/content/learning-paths/11111111-1111-1111-1111-111111111111/mastering-service-meshes-for-developers/introduction-to-service-meshes/routing-and-canary/_index.md
