Connector concept

A connector binds a local workload to listeners in remote sites. Listeners and connectors are matched using routing keys.

The connector model
The routing key model

A site has zero or more connectors. Each connector has an associated workload and routing key. The workload can be specified as a Kubernetes pod selector or as the host and port of a local network service. The routing key is a string identifier that binds the connector to listeners in remote sites.

On Kubernetes, the workload is usually specified using a pod selector. On Docker, Podman, and Linux, it is specified using a host and port.

Client connections forwarded to servers

Skupper routers forward client connections across the network from listeners to connectors with matching routing keys. The connectors then forward the client connections to the workload servers.

A database service with connectors in two sites