Skip to main content
Version: 1.3.x

Organization Setting

Organization Setting allows configuring global settings for the organization. Settings such as network reachability or regional failover that apply globally to the organization are configured in the Organizations Setting object.

This is a global object that uniquely configures the organization, and there can be only one Organization Setting object defined for each organization.

The following example shows how these settings can be used to describe the organization's network reachability settings and some regional failover configurations.

kind: OrganizationSetting
name: org-settings
organization: myorg
vpc01: vpc02,vpc03
- from: us-east1
to: us-central1


Settings that apply globally to the entire organization.

FieldDescriptionValidation Rule


Reachability between clusters on various networks.


List of tetrateio.api.tsb.types.v2.RegionalFailover
Default locality routing settings for all gateways.

Explicitly specify the region traffic will land on when endpoints in local region becomes unhealthy. Should be used together with OutlierDetection to detect unhealthy endpoints. Note: if no OutlierDetection specified, this will not take effect.


Network related settings for clusters.

FieldDescriptionValidation Rule


map<string, string>
Reachability between clusters on various networks. Each cluster has a "network" field representing a network boundary like a VPC on AWS/GCP/Azure. All clusters within the same network are assumed to be reachable to each other for multi-cluster routing. In addition, you can specify additional connectivity between various networks in the mesh here. For example on AWS, each VPC can be treated as a distinct network. VPCs that are reachable to one another (through peering or transit gateways) can be listed as reachable networks. The key is the network name and the value is a comma separated list of networks whose clusters are reachable from this network. e.g., vpc01: vpc02,vpc03