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: input/kube-cli/service-exposure.md
+11-2Lines changed: 11 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ This section assumes you have created and linked at least two sites.
14
14
A connector binds a local workload to listeners in remote sites.
15
15
Listeners and connectors are matched using routing keys.
16
16
17
-
For more information about connectors see [Connector concept][connector]
17
+
For more information about connectors, see [Connector concept][connector].
18
18
19
19
**Procedure**
20
20
@@ -50,13 +50,19 @@ For more information about connectors see [Connector concept][connector]
50
50
51
51
There are many options to consider when creating connectors using the CLI, see [CLI Reference][cli-ref], including *frequently used* options.
52
52
53
+
**Additional information**
54
+
55
+
If you need to expose a service from another namespace, you must use YAML as described in [Creating a connector for a different namespace using YAML][attached].
56
+
53
57
<aid="kube-creating-listener-cli"></a>
54
58
<!-- Creating a listener on Kubernetes using the CLI -->
55
59
## Creating a listener using the CLI
56
60
57
61
A listener binds a local connection endpoint to connectors in remote sites.
58
62
Listeners and connectors are matched using routing keys.
59
63
64
+
For more information about listeners. see [Listener concept][listener].
65
+
60
66
**Procedure**
61
67
62
68
1. Identify a connector that you want to use.
@@ -93,5 +99,8 @@ Listeners and connectors are matched using routing keys.
93
99
94
100
There are many options to consider when creating connectors using the CLI, see [CLI Reference][cli-ref], including *frequently used* options.
0 commit comments