Service Mesh

Address of the server implementing the Istio Mesh Configuration protocol (MCP). Can be IP address or a fully qualified DNS name. Use fs:/// to specify a file-based backend with absolute path to the directory.

Use the tls_settings to specify the tls mode to use. If the MCP server uses Istio mutual TLS and shares the root CA with Pilot, specify the TLS mode as ISTIO_MUTUAL.

Optional: only one of distribute or failover can be set. Explicitly specify loadbalancing weight across different zones and geographical locations. Refer to Locality weighted load balancing If empty, the locality weight is set according to the endpoints number within it.

Optional: only failover or distribute can be set. 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.

Originating locality, ‘/’ separated, e.g. ‘region/zone/sub_zone’.

Map of upstream localities to traffic distribution weights. The sum of all weights should be == 100. Any locality not assigned a weight will receive no traffic.

Originating region.

Destination region the traffic will fail over to when endpoints in the ‘from’ region becomes unhealthy.

Address of the server that will be used by the proxies for policy check calls. By using different names for mixerCheckServer and mixerReportServer, it is possible to have one set of Mixer servers handle policy check calls while another set of Mixer servers handle telemetry calls.

NOTE: Omitting mixerCheckServer while specifying mixerReportServer is equivalent to setting disablePolicyChecks to true.

Address of the server that will be used by the proxies for policy report calls.

Disable policy checks by the Mixer service. Default is false, i.e. Mixer policy check is enabled by default.

Allow all traffic in cases when the Mixer policy service cannot be reached. Default is false which means the traffic is denied when the client is unable to connect to Mixer.

Enable session affinity for Envoy Mixer reports so that calls from a proxy will always target the same Mixer instance.

Port on which Envoy should listen for incoming connections from other services.

Port on which Envoy should listen for HTTP PROXY requests if set.

Connection timeout used by Envoy. (MUST BE >=1ms)

If set then set SO_KEEPALIVE on the socket to enable TCP Keepalives.

Class of ingress resources to be processed by Istio ingress controller. This corresponds to the value of “kubernetes.io/ingress.class” annotation.

Name of theKubernetes service used for the istio ingress controller.

Defines whether to use Istio ingress controller for annotated or all ingress resources.

Flag to control generation of trace spans and request IDs. Requires a trace span collector defined in the proxy configuration.

File address for the proxy access log (e.g. /dev/stdout). Empty value disables access logging.

Format for the proxy access log Empty value results in proxy’s default access log format

Encoding for the proxy access log (text or json). Default value is text.

Default proxy config used by the proxy injection mechanism operating in the mesh (e.g. Kubernetes admission controller) In case of Kubernetes, the proxy config is applied once during the injection process, and remain constant for the duration of the pod. The rest of the mesh config can be changed at runtime and config gets distributed dynamically.

Set the default behavior of the sidecar for handling outbound traffic from the application. If your application uses one or more external services that are not known apriori, setting the policy to ALLOWANY will cause the sidecars to route any unknown traffic originating from the application to its requested destination. Users are strongly encouraged to use ServiceEntries to explicitly declare any external dependencies, instead of using allowany, so that traffic to these services can be monitored.

Enables clide side policy checks.

Unix Domain Socket through which Envoy communicates with NodeAgent SDS to get key/cert for mTLS. Use secret-mount files instead of SDS if set to empty.

ConfigSource describes a source of configuration data for networking rules, and other Istio configuration artifacts. Multiple data sources can be configured for a single control plane.

The trust domain corresponds to the trust root of a system. Refer to SPIFEE-ID Fallback to old identity format(without trust domain) if not set.

Locality based load balancing distribution or failover settings.

Configures DNS refresh rate for Envoy clusters of type STRICT_DNS

REQUIRED: The set of networks inside this mesh. Each network should have a unique name and information about how to infer the endpoints in the network as well as the gateways associated with the network.

REQUIRED: The list of endpoints in the network (obtained through the constituent service registries or from CIDR ranges). All endpoints in the network are directly accessible to one another.

REQUIRED: Set of gateways associated with the network.

REQUIRED: The port associated with the gateway.

The locality associated with an explicitly specified gateway (i.e. ip)

Path to the generated configuration file directory. Proxy agent generates the actual configuration and stores it in this directory.

Path to the proxy binary

Service cluster defines the name for the service_cluster that is shared by all Envoy instances. This setting corresponds to –service-cluster flag in Envoy. In a typical Envoy deployment, the service-cluster flag is used to identify the caller, for source-based routing scenarios.

Since Istio does not assign a local service/service version to each Envoy instance, the name is same for all of them. However, the source/caller’s identity (e.g., IP address) is encoded in the –service-node flag when launching Envoy. When the RDS service receives API calls from Envoy, it uses the value of the service-node flag to compute routes that are relative to the service instances located at that IP address.

The time in seconds that Envoy will drain connections during a hot restart. MUST be >=1s (e.g., 1s/1m/1h)

The time in seconds that Envoy will wait before shutting down the parent process during a hot restart. MUST be >=1s (e.g., 1s/1m/1h). MUST BE greater than drainduration_ parameter.

Address of the discovery service exposing xDS with mTLS connection.

Connection timeout used by Envoy for supporting services. (MUST BE >=1ms)

IP Address and Port of a statsd UDP listener (e.g. 10.75.241.127:9125).

Address of the Envoy Metrics Service implementation (e.g. metrics-service:15000). See Metric Service for details about Envoy’s Metrics Service API.

Port on which Envoy should listen for administrative commands.

Authentication policy defines the global switch to control authentication for Envoy-to-Envoy communication for istio components Mixer and Pilot.

File path of custom proxy configuration, currently used by proxies in front of Mixer and Pilot.

Maximum length of name field in Envoy’s metrics. The length of the name field is determined by the length of a name field in a service and the set of labels that comprise a particular version of the service. The default value is set to 189 characters. Envoy’s internal metrics take up 67 characters, for a total of 256 character name per metric. Increase the value of this field if you find that the metrics from Envoys are truncated.

The number of worker threads to run. Default value is number of cores on the machine.

Path to the proxy bootstrap template file

The mode used to redirect inbound traffic to Envoy.

Tracing configuration to be used by the proxy.

Address of the Datadog Agent.

Address of the LightStep Satellite pool.

The LightStep access token.

True if a secure connection should be used when communicating with the pool.

Path to the trusted cacert used to authenticate the pool.

Address of the Zipkin service (e.g. zipkin:9411).