From 4499a9efa455cd6cb508fbbe7cf6dff781e37c80 Mon Sep 17 00:00:00 2001
From: Jacob Weinstock <jakobweinstock@gmail.com>
Date: Wed, 1 Nov 2023 11:10:54 -0600
Subject: [PATCH] fix linting issues

Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>
---
 docs/quickstarts/KUBERNETES.md | 44 +++++++++++++++++-----------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/docs/quickstarts/KUBERNETES.md b/docs/quickstarts/KUBERNETES.md
index ab38778..421fd4f 100644
--- a/docs/quickstarts/KUBERNETES.md
+++ b/docs/quickstarts/KUBERNETES.md
@@ -15,23 +15,23 @@ You will need to bring your own hardware (machine) for this guide.
 
 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. 
-    ```
+   ```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"
-    ```
+   ```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.
+   > 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
 
@@ -42,18 +42,18 @@ You will need to bring your own hardware (machine) for this guide.
 
 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.
-    ```
+   ```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
-    ```
+   ```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.