Skip to content

Commit

Permalink
document kcp bind commmand to allow to sync deployment in quickstart
Browse files Browse the repository at this point in the history
Signed-off-by: Paolo Dettori <dettori@us.ibm.com>
  • Loading branch information
pdettori committed Jan 30, 2023
1 parent 163da25 commit c3ca137
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ local `kind` cluster.
Run the following command to tell kcp about the `kind` cluster (replace the syncer image tag as needed):

```shell
$ kubectl kcp workload sync kind --syncer-image ghcr.io/kcp-dev/kcp/syncer:v0.8.0 -o syncer-kind-main.yaml
$ kubectl kcp workload sync kind --syncer-image ghcr.io/kcp-dev/kcp/syncer:v0.10.0 -o syncer-kind-main.yaml
Creating synctarget "kind"
Creating service account "kcp-syncer-kind-25coemaz"
Creating cluster role "kcp-syncer-kind-25coemaz" to give service account "kcp-syncer-kind-25coemaz"
Expand Down Expand Up @@ -100,6 +100,15 @@ secret/kcp-syncer-kind-25coemaz created
deployment.apps/kcp-syncer-kind-25coemaz created
```

### Bind to workload APIs and create default placement

If you are running kcp version v0.10.0 and higher, you will need to run the following commmand
to create a binding to the workload APIs export and a default placement for your physical cluster:

```shell
$ kubectl kcp bind compute root
```

### Create a deployment in kcp

Let's create a deployment in our kcp workspace and see it get synced to our cluster:
Expand Down

0 comments on commit c3ca137

Please sign in to comment.