From c8ac19f4a875672c4d2784690dba9f154a8e5e67 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Sat, 12 Aug 2023 14:48:00 +0100 Subject: [PATCH] Undo misguided correction --- .../_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md b/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md index 25ecb8485d..b5b8b82429 100644 --- a/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md +++ b/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md @@ -85,7 +85,7 @@ f017f405ff4b gcr.io/google\_containers/hyperkube-arm:v1.1.2 "/hyperkube When that’s looking good we’re able to access the master node of the Kubernetes cluster with kubectl. Kubectl for ARM can be downloaded from googleapis storage. kubectl get nodes shows which cluster nodes are registered with its status. The master node is named 127.0.0.1. ``` -$ curl -fsSL -L -o /usr/bin/kubectl https://dl.k8s.io/release/v1.1.2/bin/linux/arm/kubectl +$ curl -fsSL -o /usr/bin/kubectl https://dl.k8s.io/release/v1.1.2/bin/linux/arm/kubectl $ kubectl get nodes