Skip to content

Commit 55362f8

Browse files
committed
address PR feedback
Signed-off-by: Matthew Fisher <[email protected]>
1 parent e6aa7ab commit 55362f8

File tree

1 file changed

+15
-17
lines changed

1 file changed

+15
-17
lines changed

content/en/docs/install/linode-kubernetes-engine.md

Lines changed: 15 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ Engine (LKE).
1010

1111
## Prerequisites
1212

13-
This guide assumes that you have an Akamai Linode account that is configured and has sufficient
14-
permissions for creating a new LKE cluster.
13+
This guide assumes that you have an [Akamai Linode](https://login.linode.com/) account that is
14+
configured and has sufficient permissions for creating a new LKE cluster.
1515

1616
You will also need recent versions of `kubectl` and `helm` installed on your system.
1717

@@ -30,17 +30,19 @@ In the Linode web console, click on `Kubernetes` in the right-hand navigation, a
3030
![LKE Creation Screen Described Below](../lke-spinkube-create.png)
3131

3232
You will only need to make a few choices on this screen. Here's what we have done:
33-
* We named the cluster `spinkube-lke-1`. You should name it according to whatever convention you
34-
prefer
35-
* We chose the `Chicago, IL (us-ord)` region, but you can choose any region you prefer
36-
* The latest supported Kubernetes version is `1.30`, so we chose that
37-
* For this testing cluster, we chose `No` on `HA Control Plane` because we do not need high
38-
availability
39-
* In `Add Node Pools`, we added two `Dedicated 4 GB` simply to show a cluster running more than one
40-
node. Two nodes is sufficient for Spin apps, though you may prefer the more traditional 3 node
41-
cluster. Click `Add` to add these, and ignore the warning about minimum sizes.
42-
43-
Once you have set things to your liking, press `Create Cluster`.
33+
34+
* **Cluster name**: We named the cluster `spinkube-lke-1`. You should name it according to whatever
35+
convention you prefer.
36+
* **Region**: We chose the `Chicago, IL (us-ord)` region, but you can choose any region you prefer.
37+
* **Kubernetes Version**: The latest supported Kubernetes version is `1.30`, so we chose that.
38+
* **High Availability Control Plane**: For this testing cluster, we chose `No` on `HA Control Plane`
39+
because we do not need high availability.
40+
* **Node Pool configuration**: In `Add Node Pools`, we added two `Dedicated 4 GB` simply to show a
41+
cluster running more than one node. Two nodes is sufficient for Spin apps, though you may prefer
42+
the more traditional 3 node cluster. Click `Add` to add these, and ignore the warning about
43+
minimum sizes.
44+
45+
Once you have set things to your liking, click `Create Cluster`.
4446

4547
This will take you to a screen that shows the status of the cluster. Initially, you will want to
4648
wait for all of your `Node Pool` to start up. Once all of the nodes are online, download the
@@ -209,11 +211,7 @@ To delete this sample app, we will first delete the NodeBalancer, and then delet
209211
$ kubectl delete service spin-rust-hello-nodebalancer
210212
service "spin-rust-hello-nodebalancer" deleted
211213
$ kubectl delete spinapp spin-rust-hello
212-
<<<<<<< HEAD
213214
spinapp.core.spinkube.dev "spin-rust-hello" deleted
214-
=======
215-
spinapp.core.spinoperator.dev "spin-rust-hello" deleted
216-
>>>>>>> 517cc81 (hard wrap at 100 characters)
217215
```
218216

219217
> If you delete the NodeBalancer out of the Linode console, it will not automatically delete the

0 commit comments

Comments
 (0)