Skip to content

Commit 52b1140

Browse files
committed
quote the camel-k installation so it works on zsh
1 parent d864fb7 commit 52b1140

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

docs/versioned/bookstore/page-7/slack-sink-learning-knative-eventing-and-apache-camel-K-integration.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Install Apache Camel K operator on your cluster using any of the methods listed
2929

3030
```sh
3131
kubectl create ns camel-k && \
32-
kubectl apply -k github.com/apache/camel-k/install/overlays/kubernetes/descoped?ref=v2.8.0 --server-side
32+
kubectl apply -k 'github.com/apache/camel-k/install/overlays/kubernetes/descoped?ref=v2.8.0' --server-side
3333
```
3434

3535
Now you need to setup an `IntegrationPlatform` with a container registry. You can read more about it in [the official installation docs](https://camel.apache.org/camel-k/2.8.x/installation/installation.html#integration-platform). For all our needs we only need to create the `IntegrationPlatform` CR with a container registry entry. For example let's say we're using a Kind cluster with a local registry named `kind-registry` on port `5000`. Then your `IntegrationPlatform` CR will look like the following:
@@ -90,7 +90,6 @@ If you are using other container registries, you may need to read more in the [c
9090
You will see the output with the registry address:
9191

9292
```sh
93-
kubectl get integrationplatforms -n camel-k
9493
NAME PHASE BUILD STRATEGY PUBLISH STRATEGY REGISTRY ADDRESS DEFAULT RUNTIME CAMEL VERSION
9594
camel-k Ready routine Jib kind-registry:5000 3.15.3 4.8.5
9695
```

0 commit comments

Comments
 (0)