Merge pull request #53 from spinkube/v1alpha1

switch to core.spinoperator.dev/v1alpha1
spinkube · Mar 11, 2024 · b8fa5fe · b8fa5fe
2 parents cf2b7cc + 3a433e0
commit b8fa5fe
Show file tree

Hide file tree

Showing 6 changed files with 8 additions and 8 deletions.
diff --git a/content/en/docs/glossary/_index.md b/content/en/docs/glossary/_index.md
@@ -35,7 +35,7 @@ A Custom Resource Definition (CRD) is an extension mechanism that allows users t
 For example, the following `.yaml` file describes a `SpinApp` using CRD syntax:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1
+apiVersion: core.spinoperator.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: simple-spinapp

diff --git a/content/en/docs/spin-operator/tutorials/assigning-variables.md b/content/en/docs/spin-operator/tutorials/assigning-variables.md
@@ -89,7 +89,7 @@ The deployment manifest (`config/samples/variable-explorer.yaml`) specifies a st
 
 ```yaml
 kind: SpinApp
-apiVersion: core.spinoperator.dev/v1
+apiVersion: core.spinoperator.dev/v1alpha1
 metadata:
   name: variable-explorer
 spec:

diff --git a/content/en/docs/spin-operator/tutorials/package-and-deploy.md b/content/en/docs/spin-operator/tutorials/package-and-deploy.md
@@ -95,7 +95,7 @@ In the previous section, you deployed the `hello-spin` app using the `spin kube
 
 ```shell
 spin kube scaffold --from ttl.sh/hello-spin:24h
-apiVersion: core.spinoperator.dev/v1
+apiVersion: core.spinoperator.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: hello-spin
@@ -113,7 +113,7 @@ spin kube scaffold --from ttl.sh/hello-spin:24h \
 
 # Print contents of spinapp.yaml
 cat spinapp.yaml
-apiVersion: core.spinoperator.dev/v1
+apiVersion: core.spinoperator.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: hello-spin
@@ -172,7 +172,7 @@ spin kube scaffold --from ghcr.io/$GH_USER/hello-spin:0.0.1 \
 Before deploying the manifest with `kubectl`, update `spinapp.yaml` and link the `ghcr` secret you previously created using the `imagePullSecrets` property. Your `SpinApp` manifest should look like this:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1
+apiVersion: core.spinoperator.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: hello-spin

diff --git a/content/en/docs/spin-operator/tutorials/running-locally.md b/content/en/docs/spin-operator/tutorials/running-locally.md
@@ -73,7 +73,7 @@ created above:
 
 ```console
 kubectl apply -f - <<EOF
-apiVersion: core.spinoperator.dev/v1
+apiVersion: core.spinoperator.dev/v1alpha1
 kind: SpinAppExecutor
 metadata:
   name: containerd-shim-spin

diff --git a/content/en/docs/spin-operator/tutorials/scaling-with-hpa.md b/content/en/docs/spin-operator/tutorials/scaling-with-hpa.md
@@ -105,7 +105,7 @@ Note that the tag at the end of [ttl.sh/cpu-load-gen:1h](http://ttl.sh/cpu-load-
 We can take a look at the SpinApp and HPA definitions in our deployment file below/. As you can see, we have set our `resources` -> `limits` to `500m` of `cpu` and `500Mi` of `memory` per Spin application and we will scale the instance count when we’ve reached a 50% utilization in `cpu` and `memory`. We’ve also defined support a maximum [replica](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#replicas) count of 10 and a minimum replica count of 1:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1
+apiVersion: core.spinoperator.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: hpa-spinapp

diff --git a/content/en/docs/spin-operator/tutorials/scaling-with-keda.md b/content/en/docs/spin-operator/tutorials/scaling-with-keda.md
@@ -122,7 +122,7 @@ We can take a look at the SpinApp and the KEDA ScaledObject definitions in our d
 
 ```yaml
 # config/samples/keda-app.yaml
-apiVapiVersion: core.spinoperator.dev/v1
+apiVersion: core.spinoperator.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: keda-spinapp