From 95aca622f5f3a4d002dea6166c7343bf124996e7 Mon Sep 17 00:00:00 2001 From: oaktowner Date: Tue, 21 Oct 2014 17:10:56 -0700 Subject: [PATCH] Update k8s201.md Minor typo corrected. --- examples/walkthrough/k8s201.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/walkthrough/k8s201.md b/examples/walkthrough/k8s201.md index 1f59078587..ad181534d4 100644 --- a/examples/walkthrough/k8s201.md +++ b/examples/walkthrough/k8s201.md @@ -6,7 +6,7 @@ We'll now cover some slightly more advanced topics in Kubernetes, related to app scaling. ### Labels -Having already learned about Pods and how to create them, ou may be struck by an urge to create many, many pods. Please do! But eventually you will need a system to organize these pods into groups. The system for achieving this in Kubernetes is Labels. Labels are key-value pairs that are attached to each API object in Kubernetes. Label selectors can be passed along with a RESTful ```list``` request to the apiserver to retrieve a list of objects which match that label selector. For example: +Having already learned about Pods and how to create them, you may be struck by an urge to create many, many pods. Please do! But eventually you will need a system to organize these pods into groups. The system for achieving this in Kubernetes is Labels. Labels are key-value pairs that are attached to each API object in Kubernetes. Label selectors can be passed along with a RESTful ```list``` request to the apiserver to retrieve a list of objects which match that label selector. For example: ```sh cluster/kubecfg.sh -l name=nginx list pods