Name of the secret the certificate and its key will be stored into. If it is empty, it will not be stored into a secret. Instead, the certificate and its key will be stored into a hard-coded directory.

The DNS names for the certificate. A certificate may contain multiple DNS names.

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 tlssettings 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 ISTIOMUTUAL.

Describes the source of configuration, if nothing is specified default is MCP

Optional: only one of distribute or failover can be set. Explicitly specify loadbalancing weight across different zones and geographical locations. Refer to 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)

Automatic protocol detection uses a set of heuristics to determine whether the connection is using TLS or not (on the server side), as well as the application protocol being used (e.g., http vs tcp). These heuristics rely on the client sending the first bits of data. For server first protocols like MySQL, MongoDB, etc., Envoy will timeout on the protocol detection after the specified period, defaulting to non mTLS plain TCP traffic. Set this field to tweak the period that Envoy will wait for the client to send the first bits of data. (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.

This flag enables Envoy’s gRPC Access Log Service. See for details about Envoy’s gRPC Access Log Service API.

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 client 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

The trust domain aliases represent the aliases of trust_domain. For example, if we have

Any service with the identity td1/ns/foo/sa/a-service-account, td2/ns/foo/sa/a-service-account, or td3/ns/foo/sa/a-service-account will be treated the same in the Istio mesh.

The default value for the ServiceEntry.export_to field and services imported through container registry integrations, e.g. this applies to Kubernetes Service resources. The value is a list of namespace names and reserved namespace aliases. The allowed namespace aliases are:

• - All Namespaces . - Current Namespace ~ - No Namespace

If not set the system will use “” as the default value which implies that services are exported to all namespaces.

‘All namespaces’ is a reasonable default for implementations that don’t need to restrict access or visibility of services across namespace boundaries. If that requirement is present it is generally good practice to make the default ‘Current namespace’ so that services are only visible within their own namespaces by default. Operators can then expand the visibility of services to other namespaces as needed. Use of ‘No Namespace’ is expected to be rare but can have utility for deployments where dependency management needs to be precise even within the scope of a single namespace.

For further discussion see the reference documentation for ServiceEntry, Sidecar, and Gateway.

The default value for the VirtualService.exportto field. Has the same syntax as ‘defaultserviceexportto’.

If not set the system will use “” as the default value which implies that virtual services are exported to all namespaces

The default value for the DestinationRule.exportto field. Has the same syntax as ‘defaultserviceexportto’.

If not set the system will use “*” as the default value which implies that destination rules are exported to all namespaces

The namespace to treat as the administrative root namespace for Istio configuration. When processing a leaf namespace Istio will search for declarations in that namespace first and if none are found it will search in the root namespace. Any matching declaration found in the root namespace is processed as if it were declared in the leaf namespace.

The precise semantics of this processing are documented on each resource type.

Locality based load balancing distribution or failover settings.

Configures DNS refresh rate for Envoy clusters of type STRICT_DNS

The flag to disable report batch.

When disablereportbatch is false, this value specifies the maximum number of requests that are batched in report. If left unspecified, the default value of reportbatchmax_entries == 0 will use the hardcoded defaults of istio::mixerclient::ReportOptions.

When disablereportbatch is false, this value specifies the maximum elapsed time a batched report will be sent after a user request is processed. If left unspecified, the default reportbatchmax_time == 0 will use the hardcoded defaults of istio::mixerclient::ReportOptions.

Specify if http1.1 connections should be upgraded to http2 by default. if sidecar is installed on all pods in the mesh, then this should be set to UPGRADE. If one or more services or namespaces do not have sidecar(s), then this should be set to DONOTUPGRADE. It can be enabled by destination using the destinationRule.trafficPolicy.connectionPool.http.h2UpgradePolicy override.

Name to be used while emitting statistics for inbound clusters. By default, Istio emits statistics with the pattern inbound|||. For example inbound|7443|grpc-reviews|reviews.prod.svc.cluster.local. This can be used to override that pattern.

A Pattern can be composed of various pre-defined variables. The following variables are supported. %SERVICE% - Will be substituted with name of the service. %SERVICEFQDN% - Will be substituted with FQDN of the service. %SERVICEPORT% - Will be substituted with port of the service. %SERVICEPORTNAME% - Will be substituted with port name of the service.

Following are some examples of supported patterns for reviews. %SERVICEFQDN%%SERVICEPORT% will use reviews.prod.svc.cluster.local7443 as the stats name. %SERVICE% will use reviews.prod as the stats name.

Name to be used while emitting statistics for outbound clusters. By default, Istio emits statistics with the pattern outbound|||. For example outbound|8080|v2|reviews.prod.svc.cluster.local. This can be used to override that pattern.

A Pattern can be composed of various pre-defined variables. The following variables are supported. %SERVICE% - Will be substituted with name of the service. %SERVICEFQDN% - Will be substituted with FQDN of the service. %SERVICEPORT% - Will be substituted with port of the service. %SERVICEPORTNAME% - Will be substituted with port name of the service. %SUBSET_NAME% - Will be substituted with subset.

Following are some examples of supported patterns for reviews. %SERVICEFQDN%%SERVICEPORT% will use reviews.prod.svc.cluster.local7443 as the stats name. %SERVICE% will use reviews.prod as the stats name.

Configure the provision of certificates.

Disables Istio ingress controller.

Istio ingress controller will act on ingress resources that do not contain any annotation or whose annotations match the value specified in the ingress_class parameter described earlier. Use this mode if Istio ingress controller will be the default ingress controller for the entireKubernetes cluster.

Istio ingress controller will only act on ingress resources whose annotations match the value specified in the ingress_class parameter described earlier. Use this mode if Istio ingress controller will be a secondary ingress controller (e.g., in addition to a cloud-provided ingress controller).

outbound traffic will be restricted to services defined in the service registry as well as those defined through ServiceEntries

outbound traffic to unknown destinations will be allowed, in case there are no services or ServiceEntries for the destination port

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.

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.

Set of gateways associated with the network.

A fully qualified domain name of the gateway service. Pilot will lookup the service from the service registries in the network and obtain the endpoint IPs of the gateway from the service registry. Note that while the service name is a fully qualified domain name, it need not be resolvable outside the orchestration platform for the registry. e.g., this could be istio-ingressgateway.istio-system.svc.cluster.local.

IP address or externally resolvable DNS address associated with the gateway.

The port associated with the gateway.

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

A CIDR range for the set of endpoints in this network. The CIDR ranges for endpoints from different networks must not overlap.

Add all endpoints from the specified registry into this network. The names of the registries should correspond to the kubeconfig file name inside the secret that was used to configure the registry (Kubernetes multicluster) or supplied by MCP server.

The REDIRECT mode uses iptables REDIRECT to NAT and redirect to Envoy. This mode loses source IP addresses during redirection.

The TPROXY mode uses iptables TPROXY to redirect to Envoy. This mode preserves both the source and destination IP addresses and ports, so that they can be used for advanced filtering and manipulation. This mode also configures the sidecar to run with the CAPNETADMIN capability, which is required to use TPROXY.

Address of a remove service used for various purposes (access log receiver, metrics receiver, etc.). Can be IP address or a fully qualified DNS name.

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

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

Set to only receive service entries that are generated by the platform. These auto generated service entries are combination of services and endpoints that are generated by a specific platform e.g. k8

True if SDS is enabled.

Path of k8s service account JWT path.

Use a Zipkin tracer.

Use a LightStep tracer.

Use a Datadog tracer.

Use a Stackdriver tracer.

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).