Merge pull request #20 from deepu105/doc-improvements

Update docs for clarity and consistency

Author: bacongobbler

.gitignore

@@ -74,3 +74,6 @@ typings/
 
 # next.js build output
 .next
+
+# Hugo build lock
+.hugo_build.lock

content/howto/bootstrapping.md

@@ -160,10 +160,12 @@ users:
 
 ### Running Krustlet
 
+> If you came here from a how-to guide for a specific platform, you can skip this section and return to that guide to continue.
+
 Once you have the bootstrap config in place, you can run Krustlet:
 
 ```console
-$ KUBECONFIG=~/.krustlet/config/kubeconfig krustlet-wasi --port 3000 --bootstrap-file /path/to/your/bootstrap.conf
+$ KUBECONFIG=~/.krustlet/config/kubeconfig krustlet-wasi --port 3000 --bootstrap-file=/path/to/your/bootstrap.conf
 ```
 
 Krustlet will begin the bootstrapping process, and then **await manual

content/howto/krustlet-on-kind.md

@@ -77,10 +77,11 @@ Once you have done that, run the following commands to run Krustlet's WASI
 provider:
 
 ```console
-# Since you are running locally, this step is important. Otherwise krustlet will pick up on your
-# local config and not be able to update the node status properly
-$ export KUBECONFIG=~/.krustlet/config/kubeconfig
-$ krustlet-wasi --node-ip 172.17.0.1 --bootstrap-file=~/.krustlet/config/bootstrap.conf
+$ KUBECONFIG=~/.krustlet/config/kubeconfig \
+  krustlet-wasi \
+  --node-ip 172.17.0.1 \
+  --node-name=krustlet \
+  --bootstrap-file=${HOME}/.krustlet/config/bootstrap.conf
 ```
 
 ### Step 3a: Approving the serving CSR

content/howto/krustlet-on-microk8s.md

@@ -56,7 +56,7 @@ guide]({{< relref "../intro/install.md" >}}).
 Let's use the built in `krustlet-wasi` provider
 
 ```console
-$ ./KUBECONFIG=${PWD}/krustlet-config \
+$ KUBECONFIG=~/.krustlet/config/kubeconfig \
   krustlet-wasi \
   --node-ip=127.0.0.1 \
   --node-name=krustlet \

content/howto/krustlet-on-minikube.md

@@ -48,10 +48,11 @@ Once you have done that, run the following commands to run Krustlet's WASI
 provider:
 
 ```console
-# Since you are running locally, this step is important. Otherwise krustlet will pick up on your
-# local config and not be able to update the node status properly
-$ export KUBECONFIG=~/.krustlet/config/kubeconfig
-$ krustlet-wasi --node-ip 10.0.2.2 --bootstrap-file=~/.krustlet/config/bootstrap.conf
+$ KUBECONFIG=~/.krustlet/config/kubeconfig \
+  krustlet-wasi \
+  --node-ip 10.0.2.2 \
+  --node-name=krustlet \
+  --bootstrap-file=${HOME}/.krustlet/config/bootstrap.conf
 ```
 
 ### Step 3a: Approving the serving CSR

content/howto/krustlet-on-wsl2.md

@@ -95,10 +95,11 @@ Once you have done that, run the following commands to run Krustlet's WASI
 provider:
 
 ```console
-# Since you are running locally, this step is important. Otherwise krustlet will pick up on your
-# local config and not be able to update the node status properly
-$ export KUBECONFIG=~/.krustlet/config/kubeconfig
-$ krustlet-wasi --node-ip $mainIP --node-name krustlet --bootstrap-file=~/.krustlet/config/bootstrap.conf
+$ KUBECONFIG=~/.krustlet/config/kubeconfig \
+  krustlet-wasi \
+  --node-ip $mainIP \
+  --node-name=krustlet \
+  --bootstrap-file=${HOME}/.krustlet/config/bootstrap.conf
 ```
 
 ### Step 3a: Approving the serving CSR

content/howto/krustlet-with-inlets.md

@@ -82,10 +82,11 @@ You'll need the certificates generated from the bootstrap process for our next
 steps, so go ahead and start krustlet:
 
 ```console
-# Since you are running locally, this step is important. Otherwise krustlet will pick up on your
-# local config and not be able to update the node status properly
-export KUBECONFIG=~/.krustlet/config/kubeconfig
-krustlet-wasi --node-ip $NODE_IP --bootstrap-file=~/.krustlet/config/bootstrap.conf
+$ KUBECONFIG=~/.krustlet/config/kubeconfig \
+  krustlet-wasi \
+  --node-ip $NODE_IP \
+  --node-name=krustlet \
+  --bootstrap-file=${HOME}/.krustlet/config/bootstrap.conf
 ```
 
 Then open another terminal for the next steps.

content/intro/quickstart.md

@@ -25,6 +25,8 @@ For production use:
 
 - [Azure]({{< relref "../howto/krustlet-on-azure.md" >}})
 - [Amazon Elastic Kubernetes Service (EKS)]({{< relref "../howto/krustlet-on-eks.md" >}})
+- [Google Kubernetes Engine (GKE)]({{< relref "../howto/krustlet-on-gke.md" >}})
+- [Managed Kubernetes on DigitalOcean]({{< relref "../howto/krustlet-on-do.md" >}})
 
 For development and evaluation purposes, it may make sense to use a VM-based
 Kubernetes cluster for quick and easy setup and teardown such as