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: docs/content/setup/local-setup-with-kind.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,10 @@
2
2
3
3
This guide will walk you through setting up kube-bind between two Kubernetes clusters, where
4
4
5
-
**Backend cluster**:
5
+
***Backend cluster**:
6
6
* Deploys dex, cert-manager and kube-bind/example-backend
7
7
* Provides kube-bind compatible backend for MangoDB resources
8
-
9
-
**App cluster**:
8
+
***App cluster**:
10
9
* Provides an application consuming MangoDBs
11
10
12
11
## Pre-requisites
@@ -60,7 +59,7 @@ nodes:
60
59
- containerPort: 30080
61
60
hostPort: 8080
62
61
protocol: TCP
63
-
# DEX endpoint
62
+
# dex endpoint
64
63
- containerPort: 30556
65
64
hostPort: 5556
66
65
protocol: TCP
@@ -71,7 +70,7 @@ EOF_BackendClusterDefinition
71
70
72
71
### Step two: deploy an identity provider
73
72
74
-
kube-bind relies on OAuth2 for securely authenticating consumer and producer clusters. There are many ways to handle that in Kubernetes, for example with [DEX IDP](https://github.com/dexidp/dex). It depends on cert-manager, which we'll deploy first:
73
+
kube-bind relies on OAuth2 for securely authenticating consumer and producer clusters. There are many ways to handle that in Kubernetes, for example with [dex IDP](https://github.com/dexidp/dex). It depends on cert-manager, which we'll deploy first:
0 commit comments