Connector update command¶
Clients at this site use the connector host and port to establish connections to the remote service. The user can change port, host name, TLS secret, selector, connector type and routing key
| Platforms | Kubernetes, Docker, Podman, Linux |
|---|---|
| Waits for | Configured |
Examples¶
# Change the workload and port
$ skupper connector update database --workload deployment/mysql --port 3306
Waiting for status...
Connector "database" is configured.
# Change the routing key
$ skupper connector update backend --routing-key be2
Primary options¶
--help
boolean
help for update
--host
<string>
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.
--port
<int>
The port of the local connector -r, --routing-key string The identifier used to route traffic from listeners to connectors
--selector
<string>
A Kubernetes label selector for specifying target server pods.
--timeout
<duration>
raise an error if the operation does not complete in the given period of time (expressed in seconds). (default 1m0s)
| Default |
|
|---|
--tls-credentials
<string>
the name of a Kubernetes secret containing the generated or externally-supplied TLS credentials.
--type
<string>
The connector type. Choices: [tcp]. (default "tcp")
| Default |
| ||
|---|---|---|---|
| Choices |
|
--wait
<string>
Wait for the given status before exiting. Choices: configured, ready, none (default "configured")
| Default |
|
|---|
--workload
<string>
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
<string>
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] ```