Installing Multiple secure clients

Customers with data centers in multiple physical locations who want all of their resources that are managed by one Turbonomic SaaS server must deploy secure clients in each of their data centers. Often, the same probes (such as vCenter) must be enabled in each secure client to send the relevant data to the server instance. This use case is supported by the setup configuration that is outlined in the following steps.

Obtain the secure client site namespace.metadata.uid.

In this example, the namespace is turbonomic. If you deploy the secure client on a different namespace, update the namespace.
```
kubectl get namespace turbonomic -o jsonpath={.metadata.uid}; echo
```
The output is similar to the following example:
```
38054ab7-b127-4fe4-8689-3e62c8551977
```
Log in to your SaaS server and add the target (such as vCenter).
1. Log in to your SaaS server.
2. Navigate to Settings > Target Configuration.
3. Click New Target, select the target type, and then select the target.
4. Provide the required information and add the target. See the Target Configuration topic for the target for additional information.
Using the SwaggerUI application, get a list of targets by using the GET /targets API call.

Remove the default target_category query value, set the target_type to the type of target you added in the previous step (for example, VCENTER), and then click Execute.

The response displays the list of the added targets.

From the response, copy the uuid of the target you just added.

In this example, the uuid value is 75544255980112.

{
  "uuid": "75544255980112",
  "displayName": "target address",
  "category": "Hypervisor",
  "isProbeRegistered": false,
  "inputFields": [
    {
      "displayName": "Address",
      "name": "address",
      "value": "<target address>",
      "isMandatory": true,
      "isSecret": false,
      "isMultiline": false,
      "isTargetDisplayName": false,
      "valueType": "STRING",
      "description": "IP or FQDN of vCenter Server",
      "verificationRegex": ".*"
    },
    ...

Verify that the information is correct by using the GET /targets/{target_Uuid} API call.

Paste the uuid value that you copied from the response into the target_Uuid field and click Execute.

Update the following JSON example for your target.

Replace the uuid value with the target's uuid, and the inputFields value with the namepsace.metadata.uid value.

{
    "uuid": "<uuid value>",
    "inputFields": [
      {
        "name":"communicationBindingChannel",
        "value":"<namespace.metadata.Uid value>"
      }
    ]
}

Use the PUT /targets/{target_Uuid} API call to edit the target.

Paste the uuid value into the target_Uuid field. Then, copy the JSON example from the previous step and paste it into the body field and click Execute.

The server response (200) is similar to the following example:

Discoveries now go through Turbonomic with the communicationBindingChannel ID.

You can now select your target on the Target Configuration page and select Rediscover to update the target's status. If the channel binding was successful, the status says "Discovered."

For more information about managing targets by using the API, see Target Requests.