update readme.adoc

kurdekar · kurdekar · commit ca70154ef89b · 2020-07-01T17:38:32.000-05:00
diff --git a/lustre/SageMaker-training-using-FSxL-on-EKS/readme.adoc b/lustre/SageMaker-training-using-FSxL-on-EKS/readme.adoc
@@ -15,7 +15,7 @@ This tutorial covers how to use *Amazon FSx for Lustre persistent deployment opt
 
 == Basic Components of Kubernetes Containers
 
-First, , let’s review some basic components of Kubernetes cluster and why we need shared persistent storage. A *Pod* is the basic execution unit of a Kubernetes application and comprises of one or more containers with shared storage/network, and a specification for how to run containers. A Pod always runs on a Node and each Node is managed by a Kubernetes Master. A *Node* is a worker machine in Kubernetes and may be either a virtual or a physical machine. A Node can have multiple pods, and the Kubernetes master automatically handles scheduling the pods across the Nodes in the cluster.These set of Nodes together with components that represent the control plane form a Kubernetes cluster.
+First, let’s review some basic components of Kubernetes cluster and why we need shared persistent storage. A *Pod* is the basic execution unit of a Kubernetes application and comprises of one or more containers with shared storage/network, and a specification for how to run containers. A Pod always runs on a Node and each Node is managed by a Kubernetes Master. A *Node* is a worker machine in Kubernetes and may be either a virtual or a physical machine. A Node can have multiple pods, and the Kubernetes master automatically handles scheduling the pods across the Nodes in the cluster.These set of Nodes together with components that represent the control plane form a Kubernetes cluster.
 
 A Pod can use two types of volumes to store data: Regular and Persistent volumes. Regular volumes on Kubernetes clusters are deleted when the Pod hosting them shuts down. As a result, regular volumes are useful for storing temporary data that does not need to exist outside of the pod’s lifetime. A *persistent volume* is a cluster-wide resource that you can use to store data  beyond the lifetime of a pod. A persistent volume is hosted in its own Pod and can remain alive for as long as necessary for ongoing operations. A Pod can specify a set of shared storage Volumes. All containers in the Pod can access the shared volumes, allowing those containers to share data. Amazon offers customers a choice of *Amazon Elastic Block Store (Amazon EBS)*, *Amazon Elastic File System (Amazon EFS)* and *Amazon FSx for Lustre* *CSI drivers* to provision persistent volumes. 
 
