dcloud lb targets addAdd an instance or IP address as a target
Synopsis
dcloud lb targets add id --type type [flags]Arguments
<id>Requiredstring
Also accepted as
--id. Constraints: uuid
Flags
--typeRequiredenum
`server` for a Deutsche Cloud instance, `ip` for an address
One of:
server,ip--instance-idOptionalstring
Instance id (i-…). Required when type is server (400 without). The instance must be in your organization (400 "Instance not found") and in the load balancer’s region (400). application and public dedicated: it needs a public IPv4 (400); private dedicated: it must be in the load balancer’s VPC and have an address there (400)
Constraints: /^i-[0-9a-f]{6,32}$/
--ipOptionalstring
IPv4 address. Required when type is ip (400 without). application and public dedicated: a public address that is not the platform’s own (400); private dedicated: inside the VPC’s CIDR (400)
--use-private-ipOptionalboolean (--use-private-ip / --no-use-private-ip)
lb11/lb21/lb31, server targets: reach the instance over its private network address. Needs a load balancer created with vpcId (400). Refused (400) on application; ignored on dedicated, where the scheme decides (private: VPC address, public: public address). Default false
--target-groupOptionalstring
application load balancers: the target group this target serves (lower-case letters, digits and -, 1–32). Rules forward to a group; requests no rule matches go to `default`. Default `default`; any other value is refused (400) on the other types. At most 10 groups and 25 targets per application load balancer (400)
Constraints: /^[a-z0-9]([a-z0-9-]{0,30}[a-z0-9])?$/
Example
dcloud lb targets add id --type serverGenerated from the API description, the same one the API checks requests against and the CLI is built from.