You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/topics/selective-deployments.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,12 +21,12 @@ Selective Deployments allow you to control which components within a Spin app ar
21
21
For this tutorial, you’ll need:
22
22
23
23
-[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
26
26
27
27
## Scaffold a Specific Component from a Spin Application into a Custom Resource
28
28
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:
30
30
31
31
-`Hello` component triggered by the `/hi` route
32
32
-`Goodbye` component triggered by the `/bye` route
@@ -91,7 +91,7 @@ spec:
91
91
92
92
## Run a Selective Deployment
93
93
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:
95
95
96
96
```bash
97
97
# Deploy the spinapp.yaml using kubectl
@@ -100,7 +100,7 @@ kubectl apply -f spinapp.yaml
100
100
spinapp.core.spinkube.dev/salutations created
101
101
```
102
102
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.
104
104
105
105
```bash
106
106
kubectl port-forward svc/salutations 8083:80
@@ -120,4 +120,4 @@ curl localhost:8083/bye
120
120
# TODO include output
121
121
```
122
122
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