InlineMetadataProxy1

JSON Example

{
    "attached_logical_port_id": "string",
    "crypto_protocols": [
        "string"
    ],
    "edge_cluster_id": "string",
    "edge_cluster_member_indexes": [
        0
    ],
    "enable_standby_relocation": false,
    "metadata_server_ca_ids": [
        "string"
    ],
    "metadata_server_url": "string",
    "secret": "string"
}

string

attached_logical_port_id

Optional

id of attached logical port

array of string

crypto_protocols

Optional

The cryptographic protocols listed here are supported by the metadata proxy. The TLSv1.1 and TLSv1.2 are supported by default.

Possible values are : TLS_V1, TLS_V1_1, TLS_V1_2,

string

edge_cluster_id

Required

edge cluster uuid

array of integer

edge_cluster_member_indexes

Optional

Constraints: minItems: 0 maxItems: 2

If none is provided, the NSX will auto-select two edge-nodes from the given edge cluster. If user provides only one edge node, there will be no HA support.

boolean

enable_standby_relocation

Optional

Flag to enable the auto-relocation of standby Metadata Proxy in case of edge node failure. Only tier 1 and auto placed Metadata Proxy are considered for the relocation.

array of string

metadata_server_ca_ids

Optional

The CAs referenced here must be uploaded to the truststore using the API POST /api/v1/trust-management/certificates?action=import. User needs to ensure a correct CA for this metedata server is used. The REST API can not detect a wrong CA which was used to verify a different server. If the Metadata Proxy reports an ERROR or NO_BACKUP status, user can check the metadata proxy log at transport node for a possible CA issue.

string

metadata_server_url

Required

The URL in format scheme://host:port/path. Please note, the scheme supports only http and https as of now, port supports range 3000 - 9000, inclusive.

string

secret

Optional

secret to access metadata server

Used By

MetadataProxy