Connector resource

Binds local workloads to listeners in remote sites.

Each site can have multiple connector resources.

apiVersion: skupper.io/v2alpha1
kind: Connector

Examples

A connector in site East for the Hello World backend service:

apiVersion: skupper.io/v2alpha1
kind: Connector
metadata:
  name: backend
  namespace: hello-world-east
spec:
  routingKey: backend
  port: 8080
  selector: app=backend

Metadata properties

name

string
required

The name of the resource.

PlatformsKubernetes, Docker, Podman, Linux

Spec properties

routingKey

string
required

The identifier used to route traffic from listeners to connectors. To expose a local workload to a remote site, the remote listener and the local connector must have matching routing keys.

PlatformsKubernetes, Docker, Podman, Linux
See alsoRouting key concept

port

integer
required

The port on the target workload to forward traffic to.

PlatformsKubernetes, Docker, Podman, Linux

selector

string
frequently used

A Kubernetes label selector for specifying target server pods.

On Kubernetes, you usually want to use this. As an alternative, you can use host.

PlatformsKubernetes

Status properties