Skip to content

Commit 7485a79

Browse files
Applying language updates, including version numbers, and other suggestions from Kate
Co-authored-by: Kate Goldenring <[email protected]> Signed-off-by: MacKenzie Olson <[email protected]>
1 parent 46db51d commit 7485a79

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

content/en/docs/topics/selective-deployments.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,12 +21,12 @@ Selective Deployments allow you to control which components within a Spin app ar
2121
For this tutorial, you’ll need:
2222

2323
- [kubectl](https://kubernetes.io/docs/tasks/tools/) - the Kubernetes CLI
24-
- Kubernetes cluster with the Spin Operator v0.4 and Containerd Spin Shim v0.16 - follow the [Quickstart](../install/quickstart.md) if needed
25-
- `spin kube` plugin - follow [Installing the `spin kube` plugin](../install/spin-kube-plugin.md) if needed
24+
- Kubernetes cluster with the Spin Operator v0.4 and Containerd Spin Shim v0.17 - follow the [Quickstart](../install/quickstart.md) if needed
25+
- `spin kube` plugin v0.3 - follow [Installing the `spin kube` plugin](../install/spin-kube-plugin.md) if needed
2626

2727
## Scaffold a Specific Component from a Spin Application into a Custom Resource
2828

29-
We’ll use a sample application called "Salutations," which demonstrates greetings via two components, each responding to a unique HTTP route. If we take a look at the [application manifest](https://github.com/spinkube/spin-operator/blob/main/apps/salutations/spin.toml), we’ll see that this Spin application is comprised of two components:
29+
We’ll use a sample application called "Salutations", which demonstrates greetings via two components, each responding to a unique HTTP route. If we take a look at the [application manifest](https://github.com/spinkube/spin-operator/blob/main/apps/salutations/spin.toml), we’ll see that this Spin application is comprised of two components:
3030

3131
- `Hello` component triggered by the `/hi` route
3232
- `Goodbye` component triggered by the `/bye` route
@@ -91,7 +91,7 @@ spec:
9191
9292
## Run a Selective Deployment
9393
94-
Now you can deploy your app using kubectl apply -f as you normally would:
94+
Now you can deploy your app using `kubectl` as you normally would:
9595

9696
```bash
9797
# Deploy the spinapp.yaml using kubectl
@@ -100,7 +100,7 @@ kubectl apply -f spinapp.yaml
100100
spinapp.core.spinkube.dev/salutations created
101101
```
102102

103-
Optionally, let’s test that only our hello component is running. We’ll use port-forwarding to access our service locally:
103+
We can test that only our `hello` component is running by port-forwarding its service.
104104

105105
```bash
106106
kubectl port-forward svc/salutations 8083:80
@@ -120,4 +120,4 @@ curl localhost:8083/bye
120120
# TODO include output
121121
```
122122

123-
And there you have it! A subset of your Spin application deployed on SpinKube with no modifications to your source code. This approach lets you quickly deploy only the components you need, which can improve efficiency in environments where only specific services are required.
123+
And there you have it! You selectively deployed a subset of your Spin application to SpinKube with no modifications to your source code. This approach lets you easily deploy only the components you need, which can improve efficiency in environments where only specific services are required.

0 commit comments

Comments
 (0)