Skip to content

Commit e830d0a

Browse files
committed
add architecture diagram
Signed-off-by: Karol Szwaj <karol.szwaj@gmail.com> On-behalf-of: @SAP karol.szwaj@sap.com
1 parent be1a945 commit e830d0a

2 files changed

Lines changed: 7 additions & 5 deletions

File tree

docs/content/usage/crossplane.png

133 KB
Loading

docs/content/usage/integrations/crossplane.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,16 +9,18 @@ weight: 20
99

1010
This document provides an example deployment walkthrough showing how to integrate kube-bind with Crossplane and how to deploy a sample managed MySQL resource using two kind clusters: a provider cluster (where Crossplane runs and kube-bind backend to export APIs) and a consumer cluster (which allows to bind those APIs using kube-bind konnector).
1111

12+
![Crossplane example architecture diagram](crossplane.png)
13+
1214
1. **Install Crossplane** in your Kubernetes cluster where the kube-bind backend will run.
1315
You can follow the official installation guide [here](https://crossplane.io/docs/v1.14/getting-started/install-configure.html).
1416

1517
```bash
16-
helm repo add crossplane-stable https://charts.crossplane.io/stable
17-
helm repo update
18+
helm repo add crossplane-stable https://charts.crossplane.io/stable
19+
helm repo update
1820

19-
helm install crossplane crossplane-stable/crossplane \
20-
--namespace crossplane-system \
21-
--create-namespace
21+
helm install crossplane crossplane-stable/crossplane \
22+
--namespace crossplane-system \
23+
--create-namespace
2224
```
2325

2426
2. **Install a Crossplane provider-sql and set up the ProviderConfig.**

0 commit comments

Comments
 (0)