hard wrap at 100 characters

bacongobbler · bacongobbler · commit 517cc8198d47 · 2024-07-30T11:48:58.000-07:00
Signed-off-by: Matthew Fisher &lt;matt.fisher@fermyon.com&gt;
diff --git a/content/en/docs/install/linode-kubernetes-engine.md b/content/en/docs/install/linode-kubernetes-engine.md
@@ -5,38 +5,53 @@ date: 2024-07-23
 tags: [Installation]
 ---
 
-This guide walks through the process of installing and configuring SpinKube on Linode Kubernetes Engine (LKE).
+This guide walks through the process of installing and configuring SpinKube on Linode Kubernetes
+Engine (LKE).
 
 ## Prerequisites
 
-This guide assumes that you have an Akamai Linode account that is configured and has sufficient permissions for creating a new LKE cluster.
+This guide assumes that you have an Akamai Linode account that is configured and has sufficient
+permissions for creating a new LKE cluster.
 
 You will also need recent versions of `kubectl` and `helm` installed on your system.
 
 ## Creating an LKE Cluster
 
-LKE has a managed control plane, so you only need to create the pool of worker nodes. In this tutorial, we will create a 2-node LKE cluster using the smallest available worker nodes. This should be fine for installing SpinKube and running up to around 100 Spin apps.
+LKE has a managed control plane, so you only need to create the pool of worker nodes. In this
+tutorial, we will create a 2-node LKE cluster using the smallest available worker nodes. This should
+be fine for installing SpinKube and running up to around 100 Spin apps.
 
-You may prefer to run a larger cluster if you plan on mixing containers and Spin apps, because containers consume substantially more resources than Spin apps do.
+You may prefer to run a larger cluster if you plan on mixing containers and Spin apps, because
+containers consume substantially more resources than Spin apps do.
 
-In the Linode web console, click on `Kubernetes` in the right-hand navigation, and then click `Create Cluster`.
+In the Linode web console, click on `Kubernetes` in the right-hand navigation, and then click
+`Create Cluster`.
 
 ![LKE Creation Screen Described Below](../lke-spinkube-create.png)
 
 You will only need to make a few choices on this screen. Here's what we have done:
-* We named the cluster `spinkube-lke-1`. You should name it according to whatever convention you prefer
+* We named the cluster `spinkube-lke-1`. You should name it according to whatever convention you
+  prefer
 * We chose the `Chicago, IL (us-ord)` region, but you can choose any region you prefer
 * The latest supported Kubernetes version is `1.30`, so we chose that
-* For this testing cluster, we chose `No` on `HA Control Plane` because we do not need high availability
-* In `Add Node Pools`, we added two `Dedicated 4 GB` simply to show a cluster running more than one node. Two nodes is sufficient for Spin apps, though you may prefer the more traditional 3 node cluster. Click `Add` to add these, and ignore the warning about minimum sizes.
+* For this testing cluster, we chose `No` on `HA Control Plane` because we do not need high
+  availability
+* In `Add Node Pools`, we added two `Dedicated 4 GB` simply to show a cluster running more than one
+  node. Two nodes is sufficient for Spin apps, though you may prefer the more traditional 3 node
+  cluster. Click `Add` to add these, and ignore the warning about minimum sizes.
 
 Once you have set things to your liking, press `Create Cluster`.
 
-This will take you to a screen that shows the status of the cluster. Initially, you will want to wait for all of your `Node Pool` to start up. Once all of the nodes are online, download the `kubeconfig` file, which will be named something like `spinkube-lke-1-kubeconfig.yaml`.
+This will take you to a screen that shows the status of the cluster. Initially, you will want to
+wait for all of your `Node Pool` to start up. Once all of the nodes are online, download the
+`kubeconfig` file, which will be named something like `spinkube-lke-1-kubeconfig.yaml`.
 
-> The `kubeconfig` file will have the credentials for connecting to your new LKE cluster. Do not share that file or put it in a public place.
+> The `kubeconfig` file will have the credentials for connecting to your new LKE cluster. Do not
+> share that file or put it in a public place.
 
-For all of the subsequent operations, you will want to use the `spinkube-lke-1-kubeconfig.yaml` as your main Kubernetes configuration file. The best way to do that is to set the environment variable `KUBECONFIG` to point to that file:
+For all of the subsequent operations, you will want to use the `spinkube-lke-1-kubeconfig.yaml` as
+your main Kubernetes configuration file. The best way to do that is to set the environment variable
+`KUBECONFIG` to point to that file:
 
 ```console
 $ export KUBECONFIG=/path/to/spinkube-lke-1-kubeconfig.yaml
@@ -67,25 +82,34 @@ users:
     token: REDACTED
 ```
 
-This shows us our cluster config. You should be able to cross-reference the `lkeNNNNNN` version with what you see on your Akamai Linode dashboard.
+This shows us our cluster config. You should be able to cross-reference the `lkeNNNNNN` version with
+what you see on your Akamai Linode dashboard.
 
 ## Install SpinKube Using Helm
 
-At this point, [install SpinKube with Helm](installing-with-helm). As long as your `KUBECONFIG` environment variable is pointed at the correct cluster, the installation method documented there will work.
+At this point, [install SpinKube with Helm](installing-with-helm). As long as your `KUBECONFIG`
+environment variable is pointed at the correct cluster, the installation method documented there
+will work.
 
 Once you are done following the installation steps, return here to install a first app.
 
 ## Creating a First App
 
-We will use the `spin kube` plugin to scaffold out a new app. If you run the following command and the `kube` plugin is not installed, you will first be prompted to install the plugin. Choose `yes` to install.
+We will use the `spin kube` plugin to scaffold out a new app. If you run the following command and
+the `kube` plugin is not installed, you will first be prompted to install the plugin. Choose `yes`
+to install.
 
-We'll point to an existing Spin app, a [Hello World program written in Rust](https://github.com/fermyon/spin/tree/main/examples/http-rust), compiled to Wasm, and stored in GitHub Container Registry (GHCR):
+We'll point to an existing Spin app, a [Hello World program written in
+Rust](https://github.com/fermyon/spin/tree/main/examples/http-rust), compiled to Wasm, and stored in
+GitHub Container Registry (GHCR):
 
 ```console
 $ spin kube scaffold --from ghcr.io/spinkube/containerd-shim-spin/examples/spin-rust-hello:v0.13.0 > hello-world.yaml
 ```
 
-> Note that Spin apps, which are WebAssembly, can be [stored in most container registries](https://developer.fermyon.com/spin/v2/registry-tutorial) even though they are not Docker containers.
+> Note that Spin apps, which are WebAssembly, can be [stored in most container
+> registries](https://developer.fermyon.com/spin/v2/registry-tutorial) even though they are not
+> Docker containers.
 
 This will write the following to `hello-world.yaml`:
 
@@ -107,10 +131,11 @@ $ kubectl apply -f hello-world.yaml
 spinapp.core.spinoperator.dev/spin-rust-hello created
 ```
 
-With SpinKube, SpinApps will be deployed as `Pod` resources, so we can see the app using `kubectl get pods`:
+With SpinKube, SpinApps will be deployed as `Pod` resources, so we can see the app using `kubectl
+get pods`:
 
 ```console
-$ kubectl get pods                 
+$ kubectl get pods
 NAME                              READY   STATUS    RESTARTS   AGE
 spin-rust-hello-f6d8fc894-7pq7k   1/1     Running   0          54s
 spin-rust-hello-f6d8fc894-vmsgh   1/1     Running   0          54s
@@ -120,7 +145,9 @@ Status is listed as `Running`, which means our app is ready.
 
 ## Making An App Public with a NodeBalancer
 
-By default, Spin apps will be deployed with an internal service. But with Linode, you can provision a [NodeBalancer](https://www.linode.com/docs/products/networking/nodebalancers/) using a `Service` object. Here is a `hello-world-service.yaml` that provisions a `nodebalancer` for us:
+By default, Spin apps will be deployed with an internal service. But with Linode, you can provision
+a [NodeBalancer](https://www.linode.com/docs/products/networking/nodebalancers/) using a `Service`
+object. Here is a `hello-world-service.yaml` that provisions a `nodebalancer` for us:
 
 ```yaml
 apiVersion: v1
@@ -143,9 +170,11 @@ spec:
   sessionAffinity: None
 ```
 
-When LKE receives a `Service` whose `type` is `LoadBalancer`, it will provision a NodeBalancer for you.
+When LKE receives a `Service` whose `type` is `LoadBalancer`, it will provision a NodeBalancer for
+you.
 
-> You can customize this for your app simply by replacing all instances of `spin-rust-hello` with the name of your app.
+> You can customize this for your app simply by replacing all instances of `spin-rust-hello` with
+> the name of your app.
 
 We can create the NodeBalancer by running `kubectl apply` on the above file:
 
@@ -154,18 +183,21 @@ $ kubectl apply -f hello-world-nodebalancer.yaml
 service/spin-rust-hello-nodebalancer created
 ```
 
-Provisioning the new NodeBalancer may take a few moments, but we can get the IP address using `kubectl get service spin-rust-hello-nodebalancer`:
+Provisioning the new NodeBalancer may take a few moments, but we can get the IP address using
+`kubectl get service spin-rust-hello-nodebalancer`:
 
 ```console
 $ get service spin-rust-hello-nodebalancer
 NAME                           TYPE           CLUSTER-IP       EXTERNAL-IP       PORT(S)        AGE
 spin-rust-hello-nodebalancer   LoadBalancer   10.128.235.253   172.234.210.123   80:31083/TCP   40s
 ```
 
-The `EXTERNAL-IP` field tells us what the NodeBalancer is using as a public IP. We can now test this out over the Internet using `curl` or by entering the URL `http://172.234.210.123/hello` into your browser.
+The `EXTERNAL-IP` field tells us what the NodeBalancer is using as a public IP. We can now test this
+out over the Internet using `curl` or by entering the URL `http://172.234.210.123/hello` into your
+browser.
 
 ```console
-$ curl 172.234.210.123/hello 
+$ curl 172.234.210.123/hello
 Hello world from Spin!
 ```
 
@@ -176,10 +208,14 @@ To delete this sample app, we will first delete the NodeBalancer, and then delet
 ```console
 $ kubectl delete service spin-rust-hello-nodebalancer
 service "spin-rust-hello-nodebalancer" deleted
-$ kubectl delete spinapp spin-rust-hello             
+$ kubectl delete spinapp spin-rust-hello
 spinapp.core.spinoperator.dev "spin-rust-hello" deleted
 ```
 
-> If you delete the NodeBalancer out of the Linode console, it will not automatically delete the `Service` record in Kubernetes, which will cause inconsistencies. So it is best to use `kubectl delete service` to delete your NodeBalancer.
+> If you delete the NodeBalancer out of the Linode console, it will not automatically delete the
+> `Service` record in Kubernetes, which will cause inconsistencies. So it is best to use `kubectl
+> delete service` to delete your NodeBalancer.
 
-If you are also done with your LKE cluster, the easiest way to delete it is to log into the Akamai Linode dashboard, navigate to `Kubernetes`, and press the `Delete` button. This will destroy all of your worker nodes and deprovision the control plane.
+If you are also done with your LKE cluster, the easiest way to delete it is to log into the Akamai
+Linode dashboard, navigate to `Kubernetes`, and press the `Delete` button. This will destroy all of
+your worker nodes and deprovision the control plane.
