diff --git a/README.md b/README.md
index 3f7da4c..36c4d05 100644
--- a/README.md
+++ b/README.md
@@ -17,28 +17,24 @@ Pick the one that works best for you.
 
 ## Next Steps
 
-Now that you have a Tinkerbell stack up and running, you can start provisioning machines.
-Tinkerbell.org has a [list of guides](https://docs.tinkerbell.org/deploying-operating-systems/the-deployment/) for provisioning machines.
-You can also create your own.
-The following docs will help you get started.
+By default the Vagrant quickstart guides automatically install Ubuntu on the VM (machine1). You can provide your own OS template. To do this:
 
-1. [Example Hardware object](https://github.com/tinkerbell/tink/tree/main/config/crd/examples/hardware.yaml)
-2. [Example Template object](https://github.com/tinkerbell/tink/tree/main/config/crd/examples/template.yaml)
-   - Template [documentation](https://docs.tinkerbell.org/templates/)
-3. [Example Workflow object](https://github.com/tinkerbell/tink/tree/main/config/crd/examples/workflow.yaml)
+1. Login to the stack VM
 
-### In the Sandbox
+   ```bash
+   vagrant ssh stack
+   ```
 
-1. Add your templates
+1. Add your template. An example Template object can be found [here](https://github.com/tinkerbell/tink/tree/main/config/crd/examples/template.yaml) and more Template documentation can be found [here](https://docs.tinkerbell.org/templates/).
 
    ```bash
-   kubectl apply -f my-custom-template.yaml
+   kubectl apply -f my-OS-template.yaml
    ```
 
-2. Create the workflow
+1. Create the workflow. An example Workflow object can be found [here](https://github.com/tinkerbell/tink/tree/main/config/crd/examples/workflow.yaml).
 
    ```bash
    kubectl apply -f my-custom-workflow.yaml
    ```
 
-3. Restart the machine to provision (if using the vagrant sandbox test machine this is done by running `vagrant destroy -f machine1 && vagrant up machine1`)
+1. Restart the machine to provision (if using the vagrant sandbox test machine this is done by running `vagrant destroy -f machine1 && vagrant up machine1`)
diff --git a/docs/quickstarts/KUBERNETES.md b/docs/quickstarts/KUBERNETES.md
index d8532d9..b6676cf 100644
--- a/docs/quickstarts/KUBERNETES.md
+++ b/docs/quickstarts/KUBERNETES.md
@@ -1,3 +1,64 @@
 # Quick start guide for Kubernetes
 
-See the [README.md](https://github.com/tinkerbell/charts/tree/main/tinkerbell/stack) in the Helm chart repository for more information on how to use the Helm chart.
+This option will walk through creating a light weight Kubernetes cluster, after which you will be able to deploy the Tinkerbell stack via the Helm chart.
+You will need to bring your own hardware for this guide.
+
+## Prerequisites
+
+- [Docker](https://docs.docker.com/get-docker/)
+- [K3D](https://k3d.io/#installation)
+- [Kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+- [Helm](https://helm.sh/docs/intro/install/)
+
+## Steps
+
+1. Create a Kubernetes cluster with K3D
+
+    ```bash
+    k3d cluster create --network host --no-lb --k3s-arg "--disable=traefik,servicelb,metrics-server,local-storage"
+    # `--network host` : host network is used to allow the load balancer to advertise a layer 2 address.
+    # `--no-lb` : the K3D built in load balancer is disabled so we don't have conflicts with the stack load balancer.
+    # `--k3s-arg "--disable=traefik,servicelb,metrics-server,local-storage"` : disable the built in K3S load balancer, metrics server, and local storage. 
+    ```
+
+1. Install the Tinkerbell stack Helm chart
+
+    ```bash
+    trusted_proxies=$(kubectl get nodes -o jsonpath='{.items[*].spec.podCIDR}' | tr ' ' ',')
+    LB_IP=<specify a Load balancer IP>
+    STACK_CHART_VERSION=0.4.2
+    helm install tink-stack oci://ghcr.io/tinkerbell/charts/stack --version "$STACK_CHART_VERSION" --create-namespace --namespace tink-system --wait --set "smee.trustedProxies={${trusted_proxies}}" --set "hegel.trustedProxies={${trusted_proxies}}" --set "stack.loadBalancerIP=$LB_IP" --set "smee.publicIP=$LB_IP"
+    ```
+
+    > These instructions above should be checked against the Charts repo before using. See the [README.md](https://github.com/tinkerbell/charts/tree/main/tinkerbell/stack) in the Helm chart repository for more information on how to use the Helm chart.
+
+1. Verify the stack is up and running
+
+   ```bash
+   kubectl get pods -n tink-system # verify all pods are running
+   kubectl get svc -n tink-system # Verify the tink-stack service has the IP you specified with $LB_IP under the EXTERNAL-IP column
+   ```
+
+1. Download and convert a cloud image to a raw image
+
+    ```bash
+    kubectl apply -f https://raw.githubusercontent.com/tinkerbell/sandbox/main/vagrant/ubuntu-download.yaml
+    # This will download and convert the Ubuntu Jammy 22.04 cloud image.
+    ```
+
+1. Create and/or customize Hardware, Template, and Workflow objects and apply them to the cluster. You can use the Hardware, Template, and Workflow in this repo, in the `vagrant/` directory, as a base from which to start.
+
+    ```bash
+    kubectl apply -f my-hardware.yaml
+    kubectl apply -f my-template.yaml
+    kubectl apply -f my-workflow.yaml
+    ```
+
+1. Start the machine provision process by rebooting, into a netbooting state, the machine you have specified in the Hardware object above.
+
+1. Watch the progress of the workflow.
+
+   ```bash
+   kubectl get workflow -n tink-system --watch
+   # Once the workflow is state is `STATE_SUCCESS`, you can login to the machine via the console or via SSH.
+   ```