chore(*): bump spin-operator to 0.6.1

Signed-off-by: Vaughn Dice <[email protected]>

Author: vdice

content/en/docs/contrib/troubleshooting.md

@@ -21,20 +21,20 @@ The error would look something like the following:
 
 ```console
 helm install spin-operator \
- --namespace spin-operator --create-namespace --version 0.6.0 --wait oci://ghcr.io/spinframework/charts/spin-operator
-Error: INSTALLATION FAILED: failed to download "oci://ghcr.io/spinframework/charts/spin-operator" at version "0.6.0"
+ --namespace spin-operator --create-namespace --version 0.6.1 --wait oci://ghcr.io/spinframework/charts/spin-operator
+Error: INSTALLATION FAILED: failed to download "oci://ghcr.io/spinframework/charts/spin-operator" at version "0.6.1"
 ```
 
 To fix, either re-authenticate with the registry with a valid token (e.g. `docker login ghcr.io`) or log out of the registry and pull the chart anonymously (e.g. `docker logout ghcr.io`).
 
 ## No endpoints available for service "spin-operator-webhook-service"
 
 When following the quickstart guide the following error can occur when running the `kubectl apply -f
-https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.shim-executor.yaml`
+https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.shim-executor.yaml`
 command:
 
 ```console
-Error from server (InternalError): error when creating "https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.shim-executor.yaml": Internal error occurred: failed calling webhook "mspinappexecutor.kb.io": failed to call webhook: Post "https://spin-operator-webhook-service.spin-operator.svc:443/mutate-core-spinkube-dev-v1alpha1-spinappexecutor?timeout=10s": no endpoints available for service "spin-operator-webhook-service"
+Error from server (InternalError): error when creating "https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.shim-executor.yaml": Internal error occurred: failed calling webhook "mspinappexecutor.kb.io": failed to call webhook: Post "https://spin-operator-webhook-service.spin-operator.svc:443/mutate-core-spinkube-dev-v1alpha1-spinappexecutor?timeout=10s": no endpoints available for service "spin-operator-webhook-service"
 ```
 
 To address the error above, first look to see if Spin Operator is running:
@@ -80,13 +80,13 @@ To resolve this issue, please try to install the Spin Operator again. Except thi
 helm upgrade --install spin-operator \
   --namespace spin-operator \
   --create-namespace \
-  --version 0.6.0 \
+  --version 0.6.1 \
   --wait \
   oci://ghcr.io/spinframework/charts/spin-operator
 ```
 
 Once the Spin Operator is installed you can try and run the `kubectl apply -f
-https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.shim-executor.yaml`
+https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.shim-executor.yaml`
 command again. The issue should be resolved now.
 
 ## Error Validating Data: Connection Refused

content/en/docs/install/azure-kubernetes-service.md

@@ -85,10 +85,10 @@ installed.
 
 ```shell
 # Install the CRDs
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.crds.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.crds.yaml
 
 # Install the Runtime Class
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.runtime-class.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.runtime-class.yaml
 ```
 
 The following installs [cert-manager](https://github.com/cert-manager/cert-manager) which is
@@ -150,15 +150,15 @@ namespace:
 helm install spin-operator \
   --namespace spin-operator \
   --create-namespace \
-  --version 0.6.0 \
+  --version 0.6.1 \
   --wait \
   oci://ghcr.io/spinframework/charts/spin-operator
 ```
 
 Lastly, create the [shim executor]({{< ref "glossary#spin-app-executor-crd" >}})::
 
 ```console
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.shim-executor.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.shim-executor.yaml
 ```
 
 ## Deploying a Spin App to AKS

content/en/docs/install/installing-with-helm.md

@@ -62,23 +62,23 @@ here we install the defaults.
   representing Spin applications to be scheduled on the cluster.
 
 ```shell
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.crds.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.crds.yaml
 ```
 
 - Next we create a [RuntimeClass]({{< ref "glossary#runtime-class" >}}) that points to the `spin`
   handler called `wasmtime-spin-v2`. If you are deploying to a production cluster that only has a shim
   on a subset of nodes, you'll need to modify the RuntimeClass with a `nodeSelector:`:
 
 ```shell
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.runtime-class.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.runtime-class.yaml
 ```
 
 - Finally, we create a `containerd-spin-shim` [SpinAppExecutor]({{< ref
   "glossary#spin-app-executor-crd" >}}). This tells the Spin Operator to use the RuntimeClass we
   just created to run Spin Apps:
 
 ```shell
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.shim-executor.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.shim-executor.yaml
 ```
 
 ### Installing the Spin Operator Chart
@@ -90,7 +90,7 @@ The following installs the chart with the release name `spin-operator`:
 helm install spin-operator \
   --namespace spin-operator \
   --create-namespace \
-  --version 0.6.0 \
+  --version 0.6.1 \
   --wait \
   oci://ghcr.io/spinframework/charts/spin-operator
 ```
@@ -101,7 +101,7 @@ Note that you may also need to upgrade the spin-operator CRDs in tandem with upg
 release:
 
 ```shell
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.crds.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.crds.yaml
 ```
 
 To upgrade the `spin-operator` release, run the following:
@@ -110,7 +110,7 @@ To upgrade the `spin-operator` release, run the following:
 # Upgrade Spin Operator using Helm
 helm upgrade spin-operator \
   --namespace spin-operator \
-  --version 0.6.0 \
+  --version 0.6.1 \
   --wait \
   oci://ghcr.io/spinframework/charts/spin-operator
 ```
@@ -130,7 +130,7 @@ To completely uninstall all resources related to spin-operator, you may want to
 corresponding CRD resources and the RuntimeClass:
 
 ```shell
-kubectl delete -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.shim-executor.yaml
-kubectl delete -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.runtime-class.yaml
-kubectl delete -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.crds.yaml
+kubectl delete -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.shim-executor.yaml
+kubectl delete -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.runtime-class.yaml
+kubectl delete -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.crds.yaml
 ```

content/en/docs/install/microk8s.md

@@ -69,8 +69,8 @@ before proceeding.
 First, we need to apply a runtime class and a CRD for SpinKube:
 
 ```console { data-plausible="copy-quick-deploy-sample" }
-$ microk8s kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.runtime-class.yaml
-$ microk8s kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.crds.yaml
+$ microk8s kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.runtime-class.yaml
+$ microk8s kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.crds.yaml
 ```
 
 Both of these should apply immediately.
@@ -90,15 +90,15 @@ $ microk8s kubectl annotate node --all kwasm.sh/kwasm-node=true
 Next, we need to install SpinKube’s operator using Helm (which is included with Microk8s).
 
 ```console { data-plausible="copy-quick-deploy-sample" }
-$ microk8s helm install spin-operator --namespace spin-operator --create-namespace --version 0.6.0 --wait oci://ghcr.io/spinframework/charts/spin-operator
+$ microk8s helm install spin-operator --namespace spin-operator --create-namespace --version 0.6.1 --wait oci://ghcr.io/spinframework/charts/spin-operator
 
 ```
 
 Now we have the main operator installed. There is just one more step. We need to install the shim
 executor, which is a special CRD that allows us to use multiple executors for WebAssembly.
 
 ```console { data-plausible="copy-quick-deploy-sample" }
-$ microk8s kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.shim-executor.yaml
+$ microk8s kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.shim-executor.yaml
 
 ```
 

content/en/docs/install/quickstart.md

@@ -55,14 +55,14 @@ kubectl wait --for=condition=available --timeout=300s deployment/cert-manager-we
 > every node.
 
 ```console { data-plausible="copy-quick-apply-runtime-class" }
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.runtime-class.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.runtime-class.yaml
 ```
 
 4. Apply the [Custom Resource Definitions]({{< ref "glossary#custom-resource-definition-crd" >}})
    used by the Spin Operator:
 
 ```console { data-plausible="copy-quick-apply-crd" }
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.crds.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.crds.yaml
 ```
 
 ## Deploy the Spin Operator
@@ -77,15 +77,15 @@ and pods are spinning up.
 helm install spin-operator \
   --namespace spin-operator \
   --create-namespace \
-  --version 0.6.0 \
+  --version 0.6.1 \
   --wait \
   oci://ghcr.io/spinframework/charts/spin-operator
 ```
 
 Lastly, create the [shim executor]({{< ref "glossary#spin-app-executor-crd" >}}):
 
 ```console { data-plausible="copy-quick-create-shim-executor" }
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.shim-executor.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.shim-executor.yaml
 ```
 
 ## Run the Sample Application

content/en/docs/install/spin-kube-plugin.md

@@ -43,7 +43,7 @@ spin plugins list --installed
 cloud 0.7.0 [installed]
 cloud-gpu 0.1.0 [installed]
 kube 0.1.1 [installed]
-pluginify 0.6.0 [installed]
+pluginify 0.6.1 [installed]
 ```
 
 ### Compiling from source

content/en/docs/reference/spin-app.md

@@ -1835,7 +1835,7 @@ A failure to resolve or pull the image during pod startup will block containers
 The types of objects that may be mounted by this volume are defined by the container runtime implementation on a host machine and at minimum must include all valid types supported by the container image field.
 The OCI object gets mounted in a single directory (spec.containers[*].volumeMounts.mountPath) by merging the manifest layers in the same way as for container images.
 The volume will be mounted read-only (ro) and non-executable files (noexec).
-Sub path mounts for containers are not supported (spec.containers[*].volumeMounts.subpath).
+Sub path mounts for containers are not supported (spec.containers[*].volumeMounts.subpath) before 1.33.
 The field spec.securityContext.fsGroupChangePolicy has no effect on this volume type.<br/>
         </td>
         <td>false</td>
@@ -3646,7 +3646,7 @@ A failure to resolve or pull the image during pod startup will block containers
 The types of objects that may be mounted by this volume are defined by the container runtime implementation on a host machine and at minimum must include all valid types supported by the container image field.
 The OCI object gets mounted in a single directory (spec.containers[*].volumeMounts.mountPath) by merging the manifest layers in the same way as for container images.
 The volume will be mounted read-only (ro) and non-executable files (noexec).
-Sub path mounts for containers are not supported (spec.containers[*].volumeMounts.subpath).
+Sub path mounts for containers are not supported (spec.containers[*].volumeMounts.subpath) before 1.33.
 The field spec.securityContext.fsGroupChangePolicy has no effect on this volume type.
 
 <table>

content/en/docs/topics/autoscaling/scaling-with-hpa.md

@@ -74,10 +74,10 @@ Next, run the following commands to install the Spin [Runtime Class]({{<ref
 
 ```console
 # Install the RuntimeClass
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.runtime-class.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.runtime-class.yaml
 
 # Install the CRDs
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.crds.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.crds.yaml
 ```
 
 Lastly, install Spin Operator using `helm` and the [shim executor]({{< ref
@@ -88,12 +88,12 @@ Lastly, install Spin Operator using `helm` and the [shim executor]({{< ref
 helm install spin-operator \
   --namespace spin-operator \
   --create-namespace \
-  --version 0.6.0 \
+  --version 0.6.1 \
   --wait \
   oci://ghcr.io/spinframework/charts/spin-operator
 
 # Install the shim executor
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.shim-executor.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.shim-executor.yaml
 ```
 
 Great, now you have Spin Operator up and running on your cluster. This means you’re set to create

content/en/docs/topics/autoscaling/scaling-with-keda.md

@@ -74,10 +74,10 @@ Next, run the following commands to install the Spin [Runtime Class]({{<ref
 
 ```console
 # Install the RuntimeClass
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.runtime-class.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.runtime-class.yaml
 
 # Install the CRDs
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.crds.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.crds.yaml
 ```
 
 Lastly, install Spin Operator using `helm` and the [shim executor]({{< ref
@@ -88,12 +88,12 @@ Lastly, install Spin Operator using `helm` and the [shim executor]({{< ref
 helm install spin-operator \
   --namespace spin-operator \
   --create-namespace \
-  --version 0.6.0 \
+  --version 0.6.1 \
   --wait \
   oci://ghcr.io/spinframework/charts/spin-operator
 
 # Install the shim executor
-kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.0/spin-operator.shim-executor.yaml
+kubectl apply -f https://github.com/spinframework/spin-operator/releases/download/v0.6.1/spin-operator.shim-executor.yaml
 ```
 
 Great, now you have Spin Operator up and running on your cluster. This means you’re set to create

crd-reference/generate.sh

@@ -9,7 +9,7 @@ script_dir=$(dirname "$0")
 
 cd $script_dir
 
-SPIN_OPERATOR_RELEASE=${SPIN_OPERATOR_RELEASE:-v0.6.0}
+SPIN_OPERATOR_RELEASE=${SPIN_OPERATOR_RELEASE:-v0.6.1}
 
 echo "Installing crdoc"
 go install fybrik.io/crdoc@latest