Este contenido no está disponible en el idioma seleccionado.
Chapter 8. Exposing services on the application network using the CLI
After creating an application network by linking sites, you can expose services from one site using connectors and consume those services on other sites using listeners. A routing key is a string that matches one or more connectors with one or more listeners. For example, if you create a connector with the routing key backend
, you need to create a listener with the routing key backend
to consume that service.
This section assumes you have created and linked at least two sites.
8.1. Creating a connector using the CLI Copiar enlaceEnlace copiado en el portapapeles!
A connector binds a local workload to listeners in remote sites. Listeners and connectors are matched using routing keys.
For more information about connectors, see Connector concept.
Procedure
Create a workload that you want to expose on the network, for example:
kubectl create deployment backend --image quay.io/skupper/hello-world-backend --replicas 3
kubectl create deployment backend --image quay.io/skupper/hello-world-backend --replicas 3
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create a connector:
skupper connector create <name> <port> [--routing-key <name>]
skupper connector create <name> <port> [--routing-key <name>]
Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example:
skupper connector create backend 8080 --workload deployment/backend
skupper connector create backend 8080 --workload deployment/backend
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check the connector status:
skupper connector status
skupper connector status
Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example:
skupper connector status
$ skupper connector status NAME STATUS ROUTING-KEY SELECTOR HOST PORT HAS MATCHING LISTENER MESSAGE backend Pending backend app=backend 8080 false No matching listeners
Copy to Clipboard Copied! Toggle word wrap Toggle overflow 📌 NOTE By default, the routing key name is set to the name of the connector. If you want to use a custom routing key, set the
--routing-key
to your custom name.
There are many options to consider when creating connectors using the CLI, see CLI Reference, including frequently used options.
Additional information
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.
8.2. Creating a listener using the CLI Copiar enlaceEnlace copiado en el portapapeles!
A listener binds a local connection endpoint to connectors in remote sites. Listeners and connectors are matched using routing keys.
For more information about listeners. see Listener concept.
Procedure
- Identify a connector that you want to use. Note the routing key of that connector.
Create a listener:
skupper connector create <name> <port> [--routing-key <name>]
skupper connector create <name> <port> [--routing-key <name>]
Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example:
skupper listener create backend 8080
$ skupper listener create backend 8080 Waiting for create to complete... Listener "backend" is ready
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check the listener status:
skupper listener status
skupper listener status
Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example:
skupper listener status
$ skupper listener status NAME STATUS ROUTING-KEY HOST PORT MATCHING-CONNECTOR MESSAGE backend Ready backend backend 8080 true OK
Copy to Clipboard Copied! Toggle word wrap Toggle overflow 📌 NOTE There must be a
MATCHING-CONNECTOR
for the service to operate. By default, the routing key name is the listener name. If you want to use a custom routing key, set the--routing-key
to your custom name.
There are many options to consider when creating connectors using the CLI, see CLI Reference, including frequently used options.