Skip to content

Commit 5c08d35

Browse files
Update Rancher Desktop install instructions to use latest release and Spin versions
Signed-off-by: Kate Goldenring <[email protected]>
1 parent ba2d9a9 commit 5c08d35

File tree

3 files changed

+30
-48
lines changed

3 files changed

+30
-48
lines changed
-443 KB
Binary file not shown.
-117 KB
Binary file not shown.

content/en/docs/install/rancher-desktop.md

Lines changed: 30 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -20,36 +20,29 @@ essentials to work with containers and Kubernetes on your desktop.
2020

2121
1. **Download Rancher Desktop**:
2222
- Navigate to the [Rancher Desktop releases
23-
page](https://github.com/rancher-sandbox/rancher-desktop/releases/tag/v1.14.0).
24-
- Select the appropriate installer for your operating system for version 1.14.0.
23+
page](https://github.com/rancher-sandbox/rancher-desktop/releases).
24+
- Select the appropriate installer for your operating system.
2525
2. **Install Rancher Desktop**:
2626
- Run the downloaded installer and follow the on-screen instructions to complete the
2727
installation.
2828

2929
### Step 2: Configure Rancher Desktop
3030

31-
- Open Rancher Desktop.
32-
- Navigate to the **Preferences** -> **Kubernetes** menu.
33-
- Ensure that the **Enable** **Kubernetes** is selected and that the **Enable Traefik** and
34-
**Install Spin Operator** Options are checked. Make sure to **Apply** your changes.
35-
36-
![Rancher Desktop](../rancher-desktop-kubernetes.png)
31+
- Open Rancher Desktop
32+
- Configure `containerd` as your container runtime engine (under **Preferences** -> **Container Engine**).
33+
- Make sure that the Enable Wasm option is checked in the **Preferences****Container Engine**
34+
section. Remember to always apply your changes.
3735

38-
- Make sure to select `rancher-desktop` from the `Kubernetes Contexts` configuration in your
39-
toolbar.
40-
41-
![Kubernetes contexts](../rancher-desktop-contexts.png)
36+
![Rancher preferences](../rancher-desktop-preferences.png)
4237

43-
- Make sure that the Enable Wasm option is checked in the **Preferences** **Container Engine
44-
section**. Remember to always apply your changes.
38+
- Navigate to the **Preferences** -> **Kubernetes** menu.
39+
- Enable Kubernetes, Traefik and Spin Operator (under **Preferences** -> **Kubernetes** ensure that the **Enable Kubernetes**, **Enable Traefik** and **Install Spin Operator** options are checked.)
4540

46-
![Rancher preferences](../rancher-desktop-preferences.png)
41+
![Rancher Desktop](../rancher-desktop-kubernetes.png)
4742

48-
- Once your changes have been applied, go to the **Cluster Dashboard****More Resources**
49-
**Cert Manager** section and click on **Certificates**. You will see the
50-
`spin-operator-serving-cert` is ready.
43+
- Make sure to select `rancher-desktop` from your Kubernetes contexts: `kubectl config use-context rancher-desktop`
5144

52-
![Certificates tab](../rancher-desktop-certificates.png)
45+
- Once your changes have been applied, go to the **Cluster Dashboard** -> **Workloads**. You should see the `spin-operator-controller-manager` deployed to the `spin-operator` namespace.
5346

5447
### Step 3: Creating a Spin Application
5548

@@ -61,17 +54,21 @@ essentials to work with containers and Kubernetes on your desktop.
6154
$ spin new -t http-js hello-k3s --accept-defaults
6255
$ cd hello-k3s
6356
```
64-
3. We can edit the `/src/index.js` file and make the workload return a string "Hello from Rancher
65-
Desktop":
57+
58+
3. We can edit the `/src/index.js` file and make the workload return a string "Hello from Rancher Desktop":
6659

6760
```javascript
68-
export async function handleRequest(request) {
69-
return {
70-
status: 200,
71-
headers: {"content-type": "text/plain"},
72-
body: "Hello from Rancher Desktop" // <-- This changed
73-
}
74-
}
61+
import { AutoRouter } from 'itty-router';
62+
63+
let router = AutoRouter();
64+
65+
router
66+
.get("/", () => new Response("Hello from Rancher Desktop")) // <-- this changed
67+
.get('/hello/:name', ({ name }) => `Hello, ${name}!`)
68+
69+
addEventListener('fetch', (event) => {
70+
event.respondWith(router.fetch(event.request));
71+
});
7572
```
7673

7774
### Step 4: Deploying Your Application
@@ -86,30 +83,15 @@ $ spin registry push ttl.sh/hello-k3s:0.1.0
8683

8784
Replace `ttl.sh/hello-k3s:0.1.0` with your registry URL and tag.
8885

89-
2. **Scaffold Kubernetes resources**:
90-
91-
```bash
92-
$ spin kube scaffold --from ttl.sh/hello-k3s:0.1.0
93-
94-
apiVersion: core.spinkube.dev/v1alpha1
95-
kind: SpinApp
96-
metadata:
97-
name: hello-k3s
98-
spec:
99-
image: "ttl.sh/hello-k3s:0.1.0"
100-
executor: containerd-shim-spin
101-
replicas: 2
102-
```
86+
2. **Deploy your Spin application to the cluster**:
10387

104-
This command prepares the necessary Kubernetes deployment configurations.
88+
Use the [`spin-kube` plugin](https://github.com/spinframework/spin-plugin-kube) to deploy your application to the cluster
10589

106-
3. **Deploy the application to Kubernetes**:
107-
108-
```bash
109-
$ spin kube deploy --from ttl.sh/hello-k3s:0.1.0
90+
```sh
91+
spin kube scaffold --from ttl.sh/hello-k3s:0.1.0 | kubectl apply -f -
11092
```
11193

112-
If we click on the Rancher Desktop’s “Cluster Dashboard”, we can see hello-k3s:0.1.0 running inside
94+
If we click on the Rancher Desktop’s “Cluster Dashboard”, we can see `hello-k3s` is running inside
11395
the “Workloads” dropdown section:
11496

11597
![Rancher Desktop Preferences Wasm](../rancher-desktop-cluster.png)

0 commit comments

Comments
 (0)