Embedding (#295)

* Create pod.yml

Signed-off-by: Lakshay Pareek <hopesalive0291@gmail.com>

* Create pod.js

Signed-off-by: Lakshay Pareek <hopesalive0291@gmail.com>

* Update _index.md

Signed-off-by: Lakshay Pareek <hopesalive0291@gmail.com>

* Delete pod.png

Signed-off-by: Lakshay Pareek <hopesalive0291@gmail.com>

---------

Signed-off-by: Lakshay Pareek <hopesalive0291@gmail.com>
Co-authored-by: Varad Gupta <114755221+vr-varad@users.noreply.github.com>

Author: Lakshay-Pareek

content/learning-paths/1e2a8e46-937c-47ea-ab43-5716e3bcab2e/end-to-end-kubernetes/intro-kubernetes/kubernetes-building-blocks/pod/_index.md

@@ -10,7 +10,10 @@ weight: 2
 
 Pods are the basic building blocks to run containers inside of Kubernetes. Every Pod holds at least one container and controls the execution of that container. If all containers terminate, the Pod terminates too. Mounting storage, setting environment variables, and feed information into the container are all functions provided by the Pod.
 
-![pod](pod.png)
+{{< meshery-design-embed
+  id="embedded-design-464cb327-ac9b-409a-a216-e8998532cf20"
+  src="pod.js"
+>}}
 
 Pods are the smallest deployable units of computing that you can create and manage in Kubernetes. Pods in a Kubernetes cluster are used in two main ways:
 
@@ -20,4 +23,4 @@ The "one-container-per-Pod" model is the most common Kubernetes use case; in thi
 
 - **Pods that run multiple containers that need to work together**
 
-A Pod can encapsulate an application composed of multiple co-located containers tightly coupled and need to share resources. These co-located containers form a single cohesive unit of service—for example, one container serving data stored in a shared volume to the public. In contrast, a separate sidecar container refreshes or updates those files. The Pod wraps these containers, storage resources, and an ephemeral network identity together as a single unit.
+A Pod can encapsulate an application composed of multiple co-located containers tightly coupled and need to share resources. These co-located containers form a single cohesive unit of service—for example, one container serving data stored in a shared volume to the public. In contrast, a separate sidecar container refreshes or updates those files. The Pod wraps these containers, storage resources, and an ephemeral network identity together as a single unit.