Connector generate command¶

skupper connector generate [options]

Clients at this site use the connector host and port to establish connections to the remote service.

Platforms	Kubernetes, Docker, Podman, Linux

Examples¶

# Generate a Connector resource and print it to the console
$ skupper connector generate backend 8080
apiVersion: skupper.io/v2alpha1
kind: Connector
metadata:
  name: backend
spec:
  routingKey: backend
  port: 8080
  selector: app=backend

# Generate a Connector resource and direct the output to a file
$ skupper connector generate backend 8080 > backend.yaml

Primary options¶

--help

boolean

help for generate

--host

The hostname or IP address of the local connector

--include-not-ready

boolean

If true, include server pods that are not in the ready state. -o, --output string print resources to the console instead of submitting them to the Skupper controller. Choices: json, yaml (default "yaml")

Default	`"yaml"`

--routing-key

The identifier used to route traffic from listeners to connectors

--selector

A Kubernetes label selector for specifying target server pods.

--tls-credentials

the name of a Kubernetes secret containing the generated or externally-supplied TLS credentials.

--type

The connector type. Choices: [tcp]. (default "tcp")

Default

"tcp"

Choices

`tcp`

--workload

A Kubernetes resource name that identifies a workload expressed like resource-type/resource-name. Expected resource types: service, daemonset, deployment, and statefulset. ``` ``` -c, --context string Set the kubeconfig context

--kubeconfig

Path to the kubeconfig file to use -n, --namespace string Set the namespace -p, --platform string Set the platform type to use [kubernetes, podman, docker, linux] ```