From f741cf5b23e9443c35f2a26becd5efff7af4ee39 Mon Sep 17 00:00:00 2001 From: Bridget Kromhout Date: Tue, 10 Apr 2018 14:33:49 -0500 Subject: [PATCH 1/5] Clarify error message upon start --- slides/kube/kubectlexpose.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/slides/kube/kubectlexpose.md b/slides/kube/kubectlexpose.md index 391e2144..a18d8ef4 100644 --- a/slides/kube/kubectlexpose.md +++ b/slides/kube/kubectlexpose.md @@ -137,7 +137,12 @@ Note: please DO NOT call the service `search`. It would collide with the TLD. -- -Our requests are load balanced across multiple pods. +We may see `curl: (7) Failed to connect to _IP_ port 9200: Connection refused` +This is normal while the service starts up + +-- + +Once it's running, our requests are load balanced across multiple pods. --- From af1347ca172e42355ab271539197df21eae0fdfe Mon Sep 17 00:00:00 2001 From: Bridget Kromhout Date: Tue, 10 Apr 2018 15:07:42 -0500 Subject: [PATCH 2/5] Clarify endpoints --- slides/kube/kubectlexpose.md | 29 ++++++++++++++++++++++++++--- 1 file changed, 26 insertions(+), 3 deletions(-) diff --git a/slides/kube/kubectlexpose.md b/slides/kube/kubectlexpose.md index a18d8ef4..dc1f2f95 100644 --- a/slides/kube/kubectlexpose.md +++ b/slides/kube/kubectlexpose.md @@ -213,12 +213,15 @@ class: extra-details ## Viewing endpoint details -- When we have many endpoints, the previous command truncates the list +- When we have many endpoints, our display commands truncate the list + ```bash + kubectl get endpoints + ``` - If we want to see the full list, we can use one of the following commands: ```bash - kubectl describe endpoint elastic - kubectl get endpoint elastic -o yaml + kubectl describe endpoints elastic + kubectl get endpoints elastic -o yaml ``` - These addresses will show us a list of IP addresses @@ -227,3 +230,23 @@ class: extra-details ```bash kubectl get pods -l run=elastic -o wide ``` + +--- + +class: extra-details + +## endpoints not endpoint + +- `endpoints` is the only resource that cannot be singular + +```bash +kubectl get endpoint +kubectl describe endpoint +``` + +-- + +.warning[error: the server doesn't have a resource type "endpoint"] + +- This is because the type itself is plural (unlike every other resource) +- There is no `endpoint` object: `type Endpoints struct` From 5ef96a29ac731a17b18c0377fa7f7531831f6941 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Petazzoni?= Date: Thu, 12 Apr 2018 00:37:18 -0500 Subject: [PATCH 3/5] Update kubectlexpose.md --- slides/kube/kubectlexpose.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/slides/kube/kubectlexpose.md b/slides/kube/kubectlexpose.md index dc1f2f95..ec655327 100644 --- a/slides/kube/kubectlexpose.md +++ b/slides/kube/kubectlexpose.md @@ -235,18 +235,17 @@ class: extra-details class: extra-details -## endpoints not endpoint +## `endpoints` not `endpoint` - `endpoints` is the only resource that cannot be singular ```bash -kubectl get endpoint -kubectl describe endpoint +$ kubectl get endpoint +error: the server doesn't have a resource type "endpoint" ``` --- - -.warning[error: the server doesn't have a resource type "endpoint"] - - This is because the type itself is plural (unlike every other resource) + - There is no `endpoint` object: `type Endpoints struct` + +- The type doesn't represent a single endpoint, but a list of endpoints From 2c3a442a4cb65cec1ce35847c36451a4bc5c6a99 Mon Sep 17 00:00:00 2001 From: Bridget Kromhout Date: Thu, 12 Apr 2018 08:11:43 -0500 Subject: [PATCH 4/5] wording correction The addresses aren't what show us the addresses - it seems clear from context that this should be "commands". --- slides/kube/kubectlexpose.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/slides/kube/kubectlexpose.md b/slides/kube/kubectlexpose.md index ec655327..4b6ef285 100644 --- a/slides/kube/kubectlexpose.md +++ b/slides/kube/kubectlexpose.md @@ -224,7 +224,7 @@ class: extra-details kubectl get endpoints elastic -o yaml ``` -- These addresses will show us a list of IP addresses +- These commands will show us a list of IP addresses - These IP addresses should match the addresses of the corresponding pods: ```bash From 56e47c35502beaaa9dd16cc240acd1cb2f5dbd3d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Petazzoni?= Date: Fri, 13 Apr 2018 08:06:23 +0200 Subject: [PATCH 5/5] Update kubectlexpose.md Add line break for readability --- slides/kube/kubectlexpose.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/slides/kube/kubectlexpose.md b/slides/kube/kubectlexpose.md index 4b6ef285..8b91773c 100644 --- a/slides/kube/kubectlexpose.md +++ b/slides/kube/kubectlexpose.md @@ -137,8 +137,9 @@ Note: please DO NOT call the service `search`. It would collide with the TLD. -- -We may see `curl: (7) Failed to connect to _IP_ port 9200: Connection refused` -This is normal while the service starts up +We may see `curl: (7) Failed to connect to _IP_ port 9200: Connection refused`. + +This is normal while the service starts up. --