Change CRD domain to spinkube.dev

adamreese · calebschoepp · commit 93ebec4d8058 · 2024-11-05T14:13:04.000-07:00
REF: spinframework/skips#5 spinframework/spin-operator#271 Signed-off-by: Adam Reese <adam@reese.io> Signed-off-by: Matthew Fisher <matt.fisher@fermyon.com>
diff --git a/content/en/docs/contrib/troubleshooting.md b/content/en/docs/contrib/troubleshooting.md
@@ -16,7 +16,7 @@ https://github.com/spinkube/spin-operator/releases/download/v0.3.0/spin-operator
 command:
 
 ```console
-Error from server (InternalError): error when creating "https://github.com/spinkube/spin-operator/releases/download/v0.3.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-spinoperator-dev-v1alpha1-spinappexecutor?timeout=10s": no endpoints available for service "spin-operator-webhook-service"
+Error from server (InternalError): error when creating "https://github.com/spinkube/spin-operator/releases/download/v0.3.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"
 ```
 
 To address the error above, first look to see if Spin Operator is running:
diff --git a/content/en/docs/glossary.md b/content/en/docs/glossary.md
@@ -74,7 +74,7 @@ SpinApp CRD consists of several key fields that define the desired state of a Sp
 Here's an example of a SpinApp custom resource that uses the SpinApp CRD schema:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: simple-spinapp
@@ -91,7 +91,7 @@ You can modify the example above to customize the SpinApp via a YAML file. Here'
 file with additional customization options:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: simple-spinapp
diff --git a/content/en/docs/install/linode-kubernetes-engine.md b/content/en/docs/install/linode-kubernetes-engine.md
@@ -114,7 +114,7 @@ $ spin kube scaffold --from ghcr.io/spinkube/containerd-shim-spin/examples/spin-
 This will write the following to `hello-world.yaml`:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: spin-rust-hello
@@ -128,7 +128,7 @@ Using `kubectl apply`, we can deploy that app:
 
 ```console
 $ kubectl apply -f hello-world.yaml
-spinapp.core.spinoperator.dev/spin-rust-hello created
+spinapp.core.spinkube.dev/spin-rust-hello created
 ```
 
 With SpinKube, SpinApps will be deployed as `Pod` resources, so we can see the app using `kubectl
@@ -157,7 +157,7 @@ metadata:
   annotations:
     service.beta.kubernetes.io/linode-loadbalancer-throttle: "4"
   labels:
-    core.spinoperator.dev/app-name: spin-rust-hello
+    core.spinkube.dev/app-name: spin-rust-hello
 spec:
   type: LoadBalancer
   ports:
@@ -166,7 +166,7 @@ spec:
     protocol: TCP
     targetPort: 80
   selector:
-    core.spinoperator.dev/app.spin-rust-hello.status: ready
+    core.spinkube.dev/app.spin-rust-hello.status: ready
   sessionAffinity: None
 ```
 
@@ -209,7 +209,7 @@ To delete this sample app, we will first delete the NodeBalancer, and then delet
 $ kubectl delete service spin-rust-hello-nodebalancer
 service "spin-rust-hello-nodebalancer" deleted
 $ kubectl delete spinapp spin-rust-hello
-spinapp.core.spinoperator.dev "spin-rust-hello" deleted
+spinapp.core.spinkube.dev "spin-rust-hello" deleted
 ```
 
 > If you delete the NodeBalancer out of the Linode console, it will not automatically delete the
diff --git a/content/en/docs/install/microk8s.md b/content/en/docs/install/microk8s.md
@@ -116,7 +116,7 @@ $ microk8s kubectl apply -f https://raw.githubusercontent.com/spinkube/spin-oper
 The above installs a simple `SpinApp` YAML that looks like this:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: simple-spinapp
diff --git a/content/en/docs/install/rancher-desktop.md b/content/en/docs/install/rancher-desktop.md
@@ -91,7 +91,7 @@ Replace `ttl.sh/hello-k3s:0.1.0` with your registry URL and tag.
 ```bash
 $ spin kube scaffold --from ttl.sh/hello-k3s:0.1.0
 
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: hello-k3s
diff --git a/content/en/docs/reference/spin-app-executor.md b/content/en/docs/reference/spin-app-executor.md
@@ -25,7 +25,7 @@ SpinAppExecutor is the Schema for the spinappexecutors API
     <tbody><tr>
       <td><b>apiVersion</b></td>
       <td>string</td>
-      <td>core.spinoperator.dev/v1alpha1</td>
+      <td>core.spinkube.dev/v1alpha1</td>
       <td>true</td>
       </tr>
       <tr>
diff --git a/content/en/docs/reference/spin-app.md b/content/en/docs/reference/spin-app.md
@@ -25,7 +25,7 @@ SpinApp is the Schema for the spinapps API
     <tbody><tr>
       <td><b>apiVersion</b></td>
       <td>string</td>
-      <td>core.spinoperator.dev/v1alpha1</td>
+      <td>core.spinkube.dev/v1alpha1</td>
       <td>true</td>
       </tr>
       <tr>
diff --git a/content/en/docs/topics/assigning-variables.md b/content/en/docs/topics/assigning-variables.md
@@ -110,7 +110,7 @@ The deployment manifest (`config/samples/variable-explorer.yaml`) specifies a st
 
 ```yaml
 kind: SpinApp
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 metadata:
   name: variable-explorer
 spec:
@@ -145,7 +145,7 @@ kubectl apply -f config/samples/variable-explorer.yaml
 
 configmap/spinapp-cfg created
 secret/spinapp-secret created
-spinapp.core.spinoperator.dev/variable-explorer created
+spinapp.core.spinkube.dev/variable-explorer created
 ```
 
 ## Inspecting runtime logs of your SpinApp
@@ -171,7 +171,7 @@ Hello from Kubernetes
 Finally, you can use `kubectl logs` to see all logs produced by the variable-explorer at runtime:
 
 ```bash
-kubectl logs -l core.spinoperator.dev/app-name=variable-explorer
+kubectl logs -l core.spinkube.dev/app-name=variable-explorer
 
 # Log Level: INFO
 # Platform Name: Kubernetes
diff --git a/content/en/docs/topics/autoscaling/scaling-with-hpa.md b/content/en/docs/topics/autoscaling/scaling-with-hpa.md
@@ -144,7 +144,7 @@ application and we will scale the instance count when we’ve reached a 50% util
 10 and a minimum replica count of 1:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: hpa-spinapp
@@ -190,7 +190,7 @@ For more information about HPA, please visit the following links:
 Below is an example of the configuration to scale resources:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: hpa-spinapp
diff --git a/content/en/docs/topics/autoscaling/scaling-with-keda.md b/content/en/docs/topics/autoscaling/scaling-with-keda.md
@@ -160,7 +160,7 @@ below. As you can see, we have explicitly specified resource limits to `500m` of
 
 ```yaml
 # https://raw.githubusercontent.com/spinkube/spin-operator/main/config/samples/keda-app.yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: keda-spinapp
@@ -212,7 +212,7 @@ command:
 ```console
 # Deploy the SpinApp
 kubectl apply -f https://raw.githubusercontent.com/spinkube/spin-operator/main/config/samples/keda-app.yaml
-spinapp.core.spinoperator.dev/keda-spinapp created
+spinapp.core.spinkube.dev/keda-spinapp created
 
 # Deploy the ScaledObject
 kubectl apply -f https://raw.githubusercontent.com/spinkube/spin-operator/main/config/samples/keda-scaledobject.yaml
diff --git a/content/en/docs/topics/connecting-to-a-sqlite-database.md b/content/en/docs/topics/connecting-to-a-sqlite-database.md
@@ -95,7 +95,7 @@ You're now ready to assemble the SpinApp custom resource manifest.
 Plug the `$IMAGE_NAME` and `$DB_URL` values into the manifest below and save as `spinapp.yaml`:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: http-crud-go-sqlite
diff --git a/content/en/docs/topics/external-variable-providers.md b/content/en/docs/topics/external-variable-providers.md
@@ -147,7 +147,7 @@ Hello from Kubernetes
 Finally, you can use `kubectl logs` to see all logs produced by the variable-explorer at runtime:
 
 ```bash
-kubectl logs -l core.spinoperator.dev/app-name=variable-explorer
+kubectl logs -l core.spinkube.dev/app-name=variable-explorer
 
 # Log Level: INFO
 # Platform Name: Kubernetes
diff --git a/content/en/docs/topics/https-requests.md b/content/en/docs/topics/https-requests.md
@@ -18,7 +18,7 @@ If you make a request without properly configured certificates, you'll encounter
 SpinKube can generate a default CA certificate bundle by setting `installDefaultCACerts` to `true`. This creates a secret named `spin-ca` populated with curl's [default bundle](https://curl.se/ca/cacert.pem). You can specify a custom secret name by setting `caCertSecret`.
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinAppExecutor
 metadata:
   name: containerd-shim-spin
@@ -46,7 +46,7 @@ kubectl create secret generic my-custom-ca --from-file=ca-certificates.crt
 Configure the executor to use the custom certificate secret:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinAppExecutor
 metadata:
   name: containerd-shim-spin
diff --git a/content/en/docs/topics/monitoring-your-app.md b/content/en/docs/topics/monitoring-your-app.md
@@ -82,7 +82,7 @@ The `SpinAppExecutor` resource determines how Spin applications are deployed in
 Create a file called `executor.yaml` with the following content:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinAppExecutor
 metadata:
   name: otel-shim-executor
@@ -108,7 +108,7 @@ With everything in place, we can now deploy a `SpinApp` resource that uses the e
 Create a file called `app.yaml` with the following content:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: otel-spinapp
diff --git a/content/en/docs/topics/packaging.md b/content/en/docs/topics/packaging.md
@@ -98,7 +98,7 @@ to your Kubernetes cluster:
 # Deploy the hello-spin app to your Kubernetes Cluster
 spin kube deploy --from ttl.sh/hello-spin:24h
 
-spinapp.core.spinoperator.dev/hello-spin created
+spinapp.core.spinkube.dev/hello-spin created
 ```
 
 ## Scaffolding Spin Apps
@@ -109,7 +109,7 @@ them. You use the `spin kube scaffold` command to generate Kubernetes manifests:
 
 ```shell
 spin kube scaffold --from ttl.sh/hello-spin:24h
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: hello-spin
@@ -128,7 +128,7 @@ spin kube scaffold --from ttl.sh/hello-spin:24h \
 
 # Print contents of spinapp.yaml
 cat spinapp.yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: hello-spin
@@ -202,7 +202,7 @@ previously created using the `imagePullSecrets` property. Your `SpinApp` manifes
 this:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: hello-spin
@@ -222,6 +222,6 @@ Finally, you can deploy the app using `kubectl apply`:
 ```shell
 # Deploy the spinapp.yaml using kubectl
 kubectl apply -f spinapp.yaml
-spinapp.core.spinoperator.dev/hello-spin created
+spinapp.core.spinkube.dev/hello-spin created
 ```
 ```
diff --git a/content/en/docs/topics/using-a-key-value-store.md b/content/en/docs/topics/using-a-key-value-store.md
@@ -92,7 +92,7 @@ You're now ready to assemble the SpinApp custom resource manifest for this appli
 Plug the `$IMAGE_NAME` and `$DB_URL` values into the manifest below and save as `spinapp.yaml`:
 
 ```yaml
-apiVersion: core.spinoperator.dev/v1alpha1
+apiVersion: core.spinkube.dev/v1alpha1
 kind: SpinApp
 metadata:
   name: kv-app
diff --git a/crd-reference/spin-app-executor-toc.yaml b/crd-reference/spin-app-executor-toc.yaml
@@ -4,7 +4,7 @@ metadata:
   description: "Custom Resource Definition (CRD) reference for `SpinAppExecutor`"
   category: Spin Operator
 groups:
-  - group: core.spinoperator.dev
+  - group: core.spinkube.dev
     version: v1alpha1
     kinds:
       - name: SpinAppExecutor
diff --git a/crd-reference/spin-app-toc.yaml b/crd-reference/spin-app-toc.yaml
@@ -3,7 +3,7 @@ metadata:
   weight: 1
   description: "Custom Resource Definition (CRD) reference for `SpinApp`"
 groups:
-  - group: core.spinoperator.dev
+  - group: core.spinkube.dev
     version: v1alpha1
     kinds:
       - name: SpinApp
