Skip to content

Commit 1011a50

Browse files
committed
More
Signed-off-by: Caleb Schoepp <[email protected]>
1 parent d21b640 commit 1011a50

File tree

1 file changed

+3
-3
lines changed
  • content/en/blog/news/five-new-things

1 file changed

+3
-3
lines changed

content/en/blog/news/five-new-things/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Since we publicly [released](/blog/2024/03/13/introducing-spinkube/) SpinKube in
1414

1515
## Selective Deployments
1616

17-
SpinKube now supports selectively deploying a subset of a Spin apps components. You select which components you would like to be a part of the deployment in the newly added `components` field of the SpinApp. Here's an example of what the YAML for a selectively deployed app might look like:
17+
SpinKube now supports selectively deploying a subset of a Spin apps components. Consider this simple example Spin application (named salutation in the [example repo](https://github.com/spinkube/spin-operator/tree/main/apps/salutations)) composed of two HTTP-triggered components: `hello` and `goodbye`. In the newly added `components` field you can select which components you would like to be a part of the deployment. Here's an example of what the YAML for a selectively deployed app might look like:
1818

1919
```yaml
2020
apiVersion: core.spinkube.dev/v1alpha1
@@ -29,7 +29,7 @@ spec:
2929
- hello
3030
```
3131
32-
We're really excited about this feature because it makes developing microservices easier. Locally develop your application as a monolith in one code base. Then, when you go to production, you can split your app based on the characteristics of each component. For example you run your front end closer to the end user while keeping your backend colocated with your database.
32+
We're really excited about this feature because it makes developing microservices easier. Locally develop your application in one code base. Then, when you go to production, you can split your app based on the characteristics of each component. For example you run your front end closer to the end user while keeping your backend colocated with your database.
3333
3434
If you want to learn more about how to use selective deployments in SpinKube checkout this [tutorial](https://www.spinkube.dev/docs/topics/selective-deployments/).
3535
@@ -65,7 +65,7 @@ If you want to learn more about how to use this new trigger checkout this [blog
6565

6666
## Spintainer Executor
6767

68-
In SpinKube there is a concept of an executor. An executor is defined by the `SpinAppExecutor` CRD and it configures how a `SpinApp` is executed. Typically you'll want to define an executor that uses the Containerd shim for Spin.
68+
In SpinKube there is a concept of an executor. An executor is defined by the `SpinAppExecutor` CRD and it configures how a `SpinApp` is run. Typically you'll want to define an executor that uses the Containerd shim for Spin.
6969

7070
```yaml
7171
apiVersion: core.spinkube.dev/v1alpha1

0 commit comments

Comments
 (0)