Connector generate command
Generate a Connector resource.
| Platforms | Kubernetes, Docker, Podman, Linux |
|---|
Usage
skupper connector generate <name> <port> [options]
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
<name>
The name of the resource to be generated.
| Platforms | Kubernetes, Docker, Podman, Linux |
|---|---|
| See also | Kubernetes object names |
<port>
The port on the target workload to forward traffic to.
| Platforms | Kubernetes, Docker, Podman, Linux |
|---|
--routing-key
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.
| Default | Value of name |
|---|---|
| Platforms | Kubernetes, Docker, Podman, Linux |
| See also | Routing key concept |
--selector
A Kubernetes label selector for specifying target server pods.
On Kubernetes, you usually want to use this. As an alternative,
you can use host.
| Default |
|
|---|---|
| Platforms | Kubernetes, Docker, Podman, Linux |
--workload
A Kubernetes resource name that identifies a workload. It resolves to an equivalent pod selector.
This is an alternative to setting the --selector or
--host options.
| Platforms | Kubernetes |
|---|---|
| See also | Kubernetes workloads |
--host
The hostname or IP address of the server. This is an
alternative to selector for specifying the target server.
| Default | Value of name |
|---|---|
| Platforms | Kubernetes, Docker, Podman, Linux |
--wait
Wait for the given status before exiting.
| Default |
| ||||||
|---|---|---|---|---|---|---|---|
| Choices |
| ||||||
| Platforms | Kubernetes, Docker, Podman, Linux |
--output
Select the output format.
| Default |
| ||||
|---|---|---|---|---|---|
| Choices |
| ||||
| Platforms | Kubernetes, Docker, Podman, Linux |
--include-not-ready
If set, include server pods that are not in the ready state.
| Default | False |
|---|---|
| Platforms | Kubernetes, Docker, Podman, Linux |
--tls-credentials
A named bundle of TLS certificates and keys used for secure application-to-router communication. The bundle contains the trusted server certificate. It optionally includes a client certificate and key for mutual TLS.
On Kubernetes, the value is the name of a Secret in the current namespace.
This option is used when setting up router-to-server TLS authentication and encryption.
| Platforms | Kubernetes, Docker, Podman, Linux |
|---|---|
| See also | Site-scoped TLS, Kubernetes TLS secrets |
Global options
--platform
Set the Skupper platform.
| Default |
| ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Choices |
| ||||||||
| Platforms | Kubernetes, Docker, Podman, Linux | ||||||||
| See also | Platform concept |
--help
Display help and exit.
| Platforms | Kubernetes, Docker, Podman, Linux |
|---|