blog: wrap at 100 characters

bacongobbler · bacongobbler · commit 148425e06f09 · 2024-08-19T08:28:23.000-07:00
Signed-off-by: Matthew Fisher &lt;matt.fisher@fermyon.com&gt;
diff --git a/content/en/about/index.md b/content/en/about/index.md
@@ -2,10 +2,9 @@
 title: SpinKube
 ---
 
-{{< blocks/cover title="Welcome to SpinKube" image_anchor="top" height="full" >}}
-<a class="btn btn-lg btn-primary me-3 mb-4" href="{{< relref "/docs" >}}">
-  SpinKube Documentation <i class="fas fa-arrow-alt-circle-right ms-2"></i>
-</a>
+{{< blocks/cover title="Welcome to SpinKube" image_anchor="top" height="full" >}} <a class="btn
+btn-lg btn-primary me-3 mb-4" href="{{< relref "/docs" >}}"> SpinKube Documentation <i class="fas
+  fa-arrow-alt-circle-right ms-2"></i> </a>
 <p class="lead mt-5">A new open source project that streamlines the experience of developing, deploying, and operating Wasm workloads on Kubernetes.</p>
 {{< blocks/link-down color="info" >}}
 {{< /blocks/cover >}}
@@ -15,32 +14,48 @@ title: SpinKube
 
 SpinKube comprises the following open source projects.
 
-<br />
-<br />
+<br /> <br />
 
 <u>**Containerd Shim Spin**</u>
 
-The [Containerd Shim Spin repository](https://github.com/spinkube/containerd-shim-spin) provides shim implementations for running WebAssembly ([Wasm](https://webassembly.org/)) / Wasm System Interface ([WASI](https://github.com/WebAssembly/WASI)) workloads using [runwasi](https://github.com/deislabs/runwasi) as a library, whereby workloads built using the [Spin framework](https://github.com/fermyon/spin) can function similarly to container workloads in a Kubernetes environment.
+The [Containerd Shim Spin repository](https://github.com/spinkube/containerd-shim-spin) provides
+shim implementations for running WebAssembly ([Wasm](https://webassembly.org/)) / Wasm System
+Interface ([WASI](https://github.com/WebAssembly/WASI)) workloads using
+[runwasi](https://github.com/deislabs/runwasi) as a library, whereby workloads built using the [Spin
+framework](https://github.com/fermyon/spin) can function similarly to container workloads in a
+Kubernetes environment.
 
-<br />
-<br />
+<br /> <br />
 
 <u>**Runtime Class Manager**</u>
 
-The [Runtime Class Manager, also known as the Containerd Shim Lifecycle Operator](https://github.com/spinkube/runtime-class-manager), is designed to automate and manage the lifecycle of containerd shims in a Kubernetes environment. This includes tasks like installation, update, removal, and configuration of shims, reducing manual errors and improving reliability in managing WebAssembly (Wasm) workloads and other containerd extensions.
+The [Runtime Class Manager, also known as the Containerd Shim Lifecycle
+Operator](https://github.com/spinkube/runtime-class-manager), is designed to automate and manage the
+lifecycle of containerd shims in a Kubernetes environment. This includes tasks like installation,
+update, removal, and configuration of shims, reducing manual errors and improving reliability in
+managing WebAssembly (Wasm) workloads and other containerd extensions.
 
-<br />
-<br />
+<br /> <br />
 
 <u>**Spin Plugin for Kubernetes**</u>
 
-The [Spin plugin for Kubernetes](https://github.com/spinkube/spin-plugin-kube), known as `spin kube`, faciliates the translation of existing [Spin applications](https://developer.fermyon.com/spin) into the Kubernetes custom resource that will be deployed and managed on your cluster. This plugin works by taking your spin application manifest and scaffolding it into a Kubernetes yaml, which can be deployed and managed with `kubectl`. This allows Kubernetes to manage and run Wasm workloads in a way similar to traditional container workloads.
+The [Spin plugin for Kubernetes](https://github.com/spinkube/spin-plugin-kube), known as `spin
+kube`, faciliates the translation of existing [Spin
+applications](https://developer.fermyon.com/spin) into the Kubernetes custom resource that will be
+deployed and managed on your cluster. This plugin works by taking your spin application manifest and
+scaffolding it into a Kubernetes yaml, which can be deployed and managed with `kubectl`. This allows
+Kubernetes to manage and run Wasm workloads in a way similar to traditional container workloads.
 
-<br />
-<br />
+<br /> <br />
 
 <u>**Spin Operator**</u>
 
-The [Spin Operator](https://github.com/spinkube/spin-operator/) enables deploying Spin applications to Kubernetes. The foundation of this project is built using the [kubebuilder](https://github.com/kubernetes-sigs/kubebuilder) framework. Spin Operator defines Spin App Custom Resource Definitions (CRDs). Spin Operator watches SpinApp Custom Resources e.g. Spin app image, replicas, schedulers and other user-defined values and realizes the desired state in the Kubernetes cluster. Spin Operator introduces a host of functionality such as resource-based scaling, event-driven scaling, and much more.
+The [Spin Operator](https://github.com/spinkube/spin-operator/) enables deploying Spin applications
+to Kubernetes. The foundation of this project is built using the
+[kubebuilder](https://github.com/kubernetes-sigs/kubebuilder) framework. Spin Operator defines Spin
+App Custom Resource Definitions (CRDs). Spin Operator watches SpinApp Custom Resources e.g. Spin app
+image, replicas, schedulers and other user-defined values and realizes the desired state in the
+Kubernetes cluster. Spin Operator introduces a host of functionality such as resource-based scaling,
+event-driven scaling, and much more.
 
 {{% /blocks/lead %}}
diff --git a/content/en/blog/community/spinkube-kind-rd/index.md b/content/en/blog/community/spinkube-kind-rd/index.md
@@ -10,7 +10,9 @@ resources:
     title: "Image #:counter"
 ---
 
-The goal of this guide is show a way to bring [SpinKube](https://www.spinkube.dev/) to [KinD](https://kind.sigs.k8s.io/) without the need of a custom image, like the [SpinKube on k3d](https://www.spinkube.dev/docs/spin-operator/quickstart/) example.
+The goal of this guide is show a way to bring [SpinKube](https://www.spinkube.dev/) to
+[KinD](https://kind.sigs.k8s.io/) without the need of a custom image, like the [SpinKube on
+k3d](https://www.spinkube.dev/docs/spin-operator/quickstart/) example.
 
 Instead, the Rancher Desktop (RD) Spin plugin will be used alongside KinD cluster configuration.
 
@@ -34,26 +36,31 @@ In order to follow this guide, the following applications need to be installed:
       - Kubernetes is disabled
 - KinD v0.23
   - This is the first version with the `nerdctl` provider
-  - If not yet available, you might need to build it (see [Bonus 1: build KinD](#bonus-1-build-kind))
+  - If not yet available, you might need to build it (see [Bonus 1: build
+    KinD](#bonus-1-build-kind))
 
 Concerning the Kubernetes tooling, Rancher Desktop already covers it.
 
 ### Connecting the Dots
 
-The reason KinD v0.23 is needed with the `nerdctl` provider is because the Spin plugin only works on Rancher Desktop when `containerd` runtime is selected, instead of `docker`.
+The reason KinD v0.23 is needed with the `nerdctl` provider is because the Spin plugin only works on
+Rancher Desktop when `containerd` runtime is selected, instead of `docker`.
 
-If it's still "obscure", keep reading and hopefully it will make sense (yes, not yet spoiling how the Spin plugin will be leveraged).
+If it's still "obscure", keep reading and hopefully it will make sense (yes, not yet spoiling how
+the Spin plugin will be leveraged).
 
 ## KinD Configurations
 
 This section should clarify how the Spin plugin will be leveraged.
 
 ### Containerd Configuration File
 
-The first configuration is related to `containerd`, and more precisely, the one running inside the KinD container(s):
+The first configuration is related to `containerd`, and more precisely, the one running inside the
+KinD container(s):
 
 - Create a file in your `$HOME` directory called `config.toml`
-  - You can create it inside a directory, however it still should be located in your `$HOME` directory
+  - You can create it inside a directory, however it still should be located in your `$HOME`
+    directory
   - The location will be important when creating the KinD cluster
 - Paste the following content inside the `config.toml` file:
 
@@ -100,20 +107,22 @@ version = 2
   tolerate_missing_hugepages_controller = true
   # restrict_oom_score_adj needs to be true when running inside UserNS (rootless)
   restrict_oom_score_adj = false
-  
+
 [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.spin]
   runtime_type = "/usr/local/bin/containerd-shim-spin-v2"
 
 ```
 
-> NOTE: this file is a copy of the original one that can be found inside the KinD container. The only addition to the file is the declaration of the `spin` plugin (the last 2 lines)
+> NOTE: this file is a copy of the original one that can be found inside the KinD container. The
+> only addition to the file is the declaration of the `spin` plugin (the last 2 lines)
 
 ### KinD Configuration File
 
 The second configuration file is related to KinD and will be used when creating a new cluster:
 
 - Create a file in your `$HOME` directory called `kind-spin.yaml` (for example)
-  - You can create it inside a directory, however it still should be located in your `$HOME` directory
+  - You can create it inside a directory, however it still should be located in your `$HOME`
+    directory
   - The location will be important when creating the KinD cluster
 
 **Windows Users ONLY**
@@ -152,15 +161,22 @@ EOF
 
 Rancher Desktop leverages two different technologies depending on the OS its installed.
 
-On Windows, [WSL2](https://learn.microsoft.com/en-us/windows/wsl/install) will be used and for Linux and MacOS, [Lima](https://lima-vm.io/docs/) is the preferred choice.
+On Windows, [WSL2](https://learn.microsoft.com/en-us/windows/wsl/install) will be used and for Linux
+and MacOS, [Lima](https://lima-vm.io/docs/) is the preferred choice.
 
-While both technologies run Linux in a microVM, the behaviors differ in some parts. And the mountpoints with the host system are one of these differences.
+While both technologies run Linux in a microVM, the behaviors differ in some parts. And the
+mountpoints with the host system are one of these differences.
 
-In the case of RD on WSL, the file generated is created **inside** the microVM, as nerdctl will need to have acceess to the file's path. Technically speaking, the mountpoint `/mnt/c` could also be used, however sometimes it's not available due to WSL main configuration. This way should be a bit more generic.
+In the case of RD on WSL, the file generated is created **inside** the microVM, as nerdctl will need
+to have acceess to the file's path. Technically speaking, the mountpoint `/mnt/c` could also be
+used, however sometimes it's not available due to WSL main configuration. This way should be a bit
+more generic.
 
-Concerning RD on Lima, `$HOME` is mounted inside the microVM, therefore nerdctl will already see the files, and there's not need on copying the files over like it's done for WSL.
+Concerning RD on Lima, `$HOME` is mounted inside the microVM, therefore nerdctl will already see the
+files, and there's not need on copying the files over like it's done for WSL.
 
-Finally, on both cases, the binary `containerd-shim-spin-v2` is already accessible inside the microVMs.
+Finally, on both cases, the binary `containerd-shim-spin-v2` is already accessible inside the
+microVMs.
 
 ## Create KinD Cluster
 
@@ -190,15 +206,20 @@ kind create cluster --config=$HOME/kind-spin.yaml
 
 ![KinD create cluster on *nix](lima-kind-create-cluster.png)
 
-Now that you have a KinD cluster running with the spin plugin enabled for `containerd`. However, it is not yet used by Kubernetes (`runtimeClass`). This will be done on the next section.
+Now that you have a KinD cluster running with the spin plugin enabled for `containerd`. However, it
+is not yet used by Kubernetes (`runtimeClass`). This will be done on the next section.
 
 ## Deploy SpinKube
 
-From here, you can reference the [excellent quickstart to deploy SpinKube](https://www.spinkube.dev/docs/spin-operator/quickstart/) for a detailed explanation of each step.
+From here, you can reference the [excellent quickstart to deploy
+SpinKube](https://www.spinkube.dev/docs/spin-operator/quickstart/) for a detailed explanation of
+each step.
 
-To avoid repetition, and to encourage you to go read the quickstart (and the overall SpinKube docs), the steps below will only include short descriptions:
+To avoid repetition, and to encourage you to go read the quickstart (and the overall SpinKube docs),
+the steps below will only include short descriptions:
 
->  **IMPORTANT:** the following commands are "universal", working on both powershell and bash/zsh. The "multiline characters" have been removed on purpose (\` for powershell and \\ for bash).
+>  **IMPORTANT:** the following commands are "universal", working on both powershell and bash/zsh.
+>  The "multiline characters" have been removed on purpose (\` for powershell and \\ for bash).
 
 ```shell
 # Install cert-manager
@@ -243,13 +264,19 @@ Congratulations! You have a cluster with SpinKube running.
 
 ## Conclusion
 
-First of all, THANK YOU to all the projects maintainers and contributors! Without you, there wouldn't be blogs like this one.
+First of all, THANK YOU to all the projects maintainers and contributors! Without you, there
+wouldn't be blogs like this one.
 
-Secondly, as you may know or not, this is **highly experimental**, and the main purpose was more a proof-of-concept rather than a real solution.
+Secondly, as you may know or not, this is **highly experimental**, and the main purpose was more a
+proof-of-concept rather than a real solution.
 
-Lastly, SpinKube on Rancher Desktop has been tested, both by Fermyon and SUSE, and it's suggested that you [follow this howto](https://www.spinkube.dev/docs/spin-operator/tutorials/integrating-with-rancher-desktop/) for a long-term environment.
+Lastly, SpinKube on Rancher Desktop has been tested, both by Fermyon and SUSE, and it's suggested
+that you [follow this
+howto](https://www.spinkube.dev/docs/spin-operator/tutorials/integrating-with-rancher-desktop/) for
+a long-term environment.
 
-Special thanks to Fermyon for hosting this (first) blog on SpinKube and thanks to anyone reaching this last line, you mean the world to me.
+Special thanks to Fermyon for hosting this (first) blog on SpinKube and thanks to anyone reaching
+this last line, you mean the world to me.
 
 > \>>> The Corsair <<<
 
diff --git a/content/en/blog/news/first-post/index.md b/content/en/blog/news/first-post/index.md
