GM_CONTROL_API_ZONE_NAME, and, optionally,
GM_CONTROL_API_ORG_KEYand a zone will be created using these values. This allows a bootstrap configuration to reference this
XDS_ZONE. This value should be the name of the zone with the
zone_keymatching its corresponding Grey Matter Control API objects.
zone, which is used to indicate this location.
XDS_ZONE. This value must also match the
GM_CONTROL_API_ZONE_NAME, because Control will only retrieve Envoy instances with the locality containing this zone for configuration (see below).
GM_CONTROL_API_ZONE_NAME, which is used to indicate both the name of the Grey Matter API zone for requests and the Node locality's zone of its Discovery Requests to Envoy.
zone_keycorresponding to this zone name will be populated with discovered instances.
GM_CONTROL_API_ZONE_NAMEdoes not match the name of the zone corresponding to the
zone_keyon any of the mesh objects, the objects will not be found by gm-control in its requests, thus objects in one
zonecannot reference objects in a different
node.locality.zonefield on its request set to the value of this variable. This value must match
XDS_ZONEon a service's sidecar, as only Envoy instances with this
zonein their Node locality will be retrieved from Envoy and configured via Grey Matter Control.