Consul
Service Defaults Configuration Reference
This topic describes how to configure service defaults configuration entries. The service defaults configuration entry contains common configuration settings for service mesh services, such as upstreams and gateways. Refer to Define service defaults for usage information.
Configuration model
The following outline shows how to format the service defaults configuration entry. Click on a property name to view details about the configuration.
Kind
: string | requiredName
: string | requiredNamespace
: string EnterprisePartition
: string EnterpriseMeta
: map | no defaultProtocol
: string | default:tcp
BalanceInboundConnections
: string | no defaultMode
: string | no defaultUpstreamConfig
: map | no defaultOverrides
: map | no defaultName
: string | no defaultNamespace
: string | no defaultPeer
: string | no defaultProtocol
: string | no defaultConnectTimeoutMs
: int | default:5000
MeshGateway
: map | no defaultmode
: string | no default
BalanceOutboundConnections
: string | no defaultLimits
: map | optionalMaxConnections
: integer |0
MaxPendingRequests
: integer |0
MaxConcurrentRequests
: integer |0
PassiveHealthCheck
: map | optionalInterval
: string |0s
MaxFailures
: integer |0
EnforcingConsecutive5xx
: integer |0
MaxEjectionPercent
: integer |0
BaseEjectionTime
: string |30s
Defaults
: map | no defaultProtocol
: string | no defaultConnectTimeoutMs
: int | default:5000
MeshGateway
: map | no defaultmode
: string | no default
BalanceOutboundConnections
: string | no defaultLimits
: map | optionalMaxConnections
: integer |0
MaxPendingRequests
: integer |0
MaxConcurrentRequests
: integer |0
PassiveHealthCheck
: map | optionalInterval
: string |0s
MaxFailures
: integer |0
EnforcingConsecutive5xx
: integer |100
MaxEjectionPercent
: integer |0
BaseEjectionTime
: string |30s
TransparentProxy
: map | no defaultOutboundListenerPort
: integer |15001
DialedDirectly
: boolean |false
EnvoyExtensions
: list | no defaultDestination
: map | no defaultMaxInboundConnections
: integer |0
LocalConnectTimeoutMs
: integer |0
LocalRequestTimeoutMs
: integer |0
MeshGateway
: map | no defaultMode
: string | no default
ExternalSNI
: string | no defaultExpose
: map | no defaultChecks
: boolean |false
Paths
: list | no defaultPath
: string | no defaultLocalPathPort
: integer |0
ListenerPort
: integer |0
Protocol
: string |http
Complete configuration
When every field is defined, a service-defaults configuration entry has the following form:
Kind = "service-defaults"
Name = "service_name"
Namespace = "namespace"
Partition = "partition"
Meta = {
Key = "value"
}
Protocol = "tcp"
BalanceInboundConnections = "exact_balance"
Mode = "transparent"
UpstreamConfig = {
Overrides = {
Name = "name-of-upstreams-to-override"
Namespace = "namespace-containing-upstreams-to-override"
Protocol = "http"
ConnectTimeoutMs = 100
MeshGateway = {
mode = "remote"
}
BalanceOutboundConnections = "exact_balance"
Limits = {
MaxConnections = 10
MaxPendingRequests = 50
MaxConcurrentRequests = 100
}
PassiveHealthCheck = {
Interval = "5s"
MaxFailures = 5
EnforcingConsecutive5xx = 99
MaxEjectionPercent = 10
BaseEjectionTime = "30s"
}
}
Defaults = {
Protocol = "http2"
ConnectTimeoutMs = 2000
MeshGateway = {
mode = "local"
}
BalanceOutboundConnections = "exact_balance"
Limits = {
MaxConnections = 100
MaxPendingRequests = 500
MaxConcurrentRequests = 1000
}
PassiveHealthCheck = {
Interval = "1s"
MaxFailures = 1
EnforcingConsecutive5xx = 89
MaxEjectionPercent = 10
BaseEjectionTime = "30s"
}
}
}
TransparentProxy = {
OutboundListenerPort = 15002
DialedDirectly = true
}
Destination = {
Addresses = [
"First IP address",
"Second IP address"
]
Port = 88
}
MaxInboundConnections = 100
LocalConnectTimeoutMs = 10
LocalRequestTimeoutMs = 10
MeshGateway = {
Mode = "remote"
}
ExternalSNI = "sni-server-host"
Expose = {
Checks = true
Paths = [
{
Path = "/local/dir"
LocalPathPort = 99
LocalListenerPort = 98
Protocol = "http2"
}
]
}
Specification
This section provides details about the fields you can configure in the service defaults configuration entry.
Kind
Specifies the configuration entry type.
Values
- Default: none
- This field is required.
- Data type: String value that must be set to
service-defaults
.
Name
Specifies the name of the service you are setting the defaults for.
Values
- Default: none
- This field is required.
- Data type: string
Namespace
Specifies the Consul namespace that the configuration entry applies to.
Values
- Default:
default
- Data type: string
Partition
Specifies the name of the Consul admin partition that the configuration entry applies to. Refer to Admin Partitions for additional information.
Values
- Default:
default
- Data type: string
Meta
Specifies a set of custom key-value pairs to add to the Consul KV store.
Values
- Default: none
- Data type: Map of one or more key-value pairs.
- keys: string
- values: string, integer, or float
Protocol
Specifies the default protocol for the service. In service mesh use cases, the protocol
configuration is required to enable the following features and components:
You can set the global protocol for proxies in the proxy-defaults
configuration entry, but the protocol specified in the service-defaults
configuration entry overrides the proxy-defaults
configuration.
Values
Refer to Set the default protocol for an example configuration.
BalanceInboundConnections
Specifies the strategy for allocating inbound connections to the service across Envoy proxy threads. The only supported value is exact_balance
. By default, no connections are balanced. Refer to the Envoy documentation for details.
Values
- Default: none
- Data type: string
Mode
Specifies a mode for how the service directs inbound and outbound traffic.
- Default: none
- You can specify the following string values:
direct
: The proxy's listeners must be dialed directly by the local application and other proxies.transparent
: The service captures inbound and outbound traffic and redirects it through the proxy. The mode does not enable the traffic redirection. It instructs Consul to configure Envoy as if traffic is already being redirected.
UpstreamConfig
Controls default upstream connection settings and custom overrides for individual upstream services. If your network contains federated datacenters, individual upstream configurations apply to all pairs of source and upstream destination services in the network. Refer to the following fields for details:
Values
- Default: none
- Data type: map
UpstreamConfig.Overrides[]
Specifies options that override the default upstream configurations for individual upstreams.
Values
- Default: none
- Data type: list
UpstreamConfig.Overrides[].Name
Specifies the name of the upstream service that the configuration applies to. We recommend that you do not use the *
wildcard to avoid applying the configuration to unintended upstreams.
Values
- Default: none
- Data type: string
UpstreamConfig.Overrides[].Namespace
Specifies the namespace containing the upstream service that the configuration applies to. Do not use the *
wildcard to prevent the configuration from appling to unintended upstreams.
Values
- Default: none
- Data type: string
UpstreamConfig.Overrides[].Protocol
Specifies the protocol to use for requests to the upstream listener.
We recommend configuring the protocol in the main Protocol
field of the configuration entry so that you can leverage L7 features. Setting the protocol in an upstream configuration limits L7 management functionality.
Values
- Default: none
- Data type: string
UpstreamConfig.Overrides[].ConnectTimeoutMs
Specifies how long in milliseconds that the service should attempt to establish an upstream connection before timing out.
We recommend configuring the upstream timeout in the connection_timeout
field of the service-resolver
configuration entry for the upstream destination service. Doing so enables you to leverage L7 features. Configuring the timeout in the service-defaults
upstream configuration limits L7 management functionality.
Values
- Default:
5000
- Data type: integer
UpstreamConfig.Overrides[].MeshGateway
Map that contains the default mesh gateway mode
field for the upstream. Refer to Service Mesh Proxy Configuration in the mesh gateway documentation for additional information.
Values
- Default:
none
- You can specify the following string values for the
mode
field:none
: The service does not make outbound connections through a mesh gateway. Instead, the service makes outbound connections directly to the destination services.local
: The service mesh proxy makes an outbound connection to a gateway running in the same datacenter.remote
: The service mesh proxy makes an outbound connection to a gateway running in the destination datacenter.
UpstreamConfig.Overrides[].BalanceOutboundConnections
Sets the strategy for allocating outbound connections from the upstream across Envoy proxy threads.
Values
The only supported value is exact_balance
. By default, no connections are balanced. Refer to the Envoy documentation for details.
- Default: none
- Data type: string
UpstreamConfig.Overrides[].Limits
Map that specifies a set of limits to apply to when connecting to individual upstream services.
Values
The following table describes limits you can configure:
Limit | Description | Data type | Default |
---|---|---|---|
MaxConnections | Specifies the maximum number of connections a service instance can establish against the upstream. Define this limit for HTTP/1.1 traffic. | integer | 0 |
MaxPendingRequests | Specifies the maximum number of requests that are queued while waiting for a connection to establish. An L7 protocol must be defined in the protocol field for this limit to take effect. | integer | 0 |
MaxConcurrentRequests | Specifies the maximum number of concurrent requests. Define this limit for HTTP/2 traffic. An L7 protocol must be defined in the protocol field for this limit to take effect. | integer | 0 |
Refer to the upstream configuration example for additional guidance.
UpstreamConfig.Overrides[].PassiveHealthCheck
Map that specifies a set of rules that enable Consul to remove hosts from the upstream cluster that are unreachable or that return errors.
Values
The following table describes passive health check parameters you can configure:
Limit | Description | Data type | Default |
---|---|---|---|
Interval | Specifies the time between checks. | string | 0s |
MaxFailures | Specifies the number of consecutive failures allowed per check interval. If exceeded, Consul removes the host from the load balancer. | integer | 0 |
EnforcingConsecutive5xx | Specifies a percentage that indicates how many times out of 100 that Consul ejects the host when it detects an outlier status. The outlier status is determined by consecutive errors in the 500-599 response range. | integer | 100 |
MaxEjectionPercent | Specifies the maximum percentage of an upstream cluster that Consul ejects when the proxy reports an outlier. Consul ejects at least one host when an outlier is detected regardless of the value. | integer | 10 |
BaseEjectionTime | Specifies the minimum amount of time that an ejected host must remain outside the cluster before rejoining. The real time is equal to the value of the BaseEjectionTime multiplied by the number of times the host has been ejected. | string | 30s |
UpstreamConfig.Defaults
Specifies configurations that set default upstream settings. For information about overriding the default configurations for in for individual upstreams, refer to UpstreamConfig.Overrides
.
Values
- Default: none
- Data type: map
UpstreamConfig.Defaults.Protocol
Specifies default protocol for upstream listeners.
We recommend configuring the protocol in the main Protocol
field of the configuration entry so that you can leverage L7 features. Setting the protocol in an upstream configuration limits L7 management functionality.
- Default: none
- Data type: string
UpstreamConfig.Defaults.ConnectTimeoutMs
Specifies how long in milliseconds that all services should continue attempting to establish an upstream connection before timing out.
For non-Kubernetes environments, we recommend configuring the upstream timeout in the connection_timeout
field of the service-resolver
configuration entry for the upstream destination service. Doing so enables you to leverage L7 features. Configuring the timeout in the service-defaults
upstream configuration limits L7 management functionality.
- Default:
5000
- Data type: integer
UpstreamConfig.Defaults.MeshGateway
Specifies the default mesh gateway mode
field for all upstreams. Refer to Service Mesh Proxy Configuration in the mesh gateway documentation for additional information.
You can specify the following string values for the mode
field:
none
: The service does not make outbound connections through a mesh gateway. Instead, the service makes outbound connections directly to the destination services.local
: The service mesh proxy makes an outbound connection to a gateway running in the same datacenter.remote
: The service mesh proxy makes an outbound connection to a gateway running in the destination datacenter.
UpstreamConfig.Defaults.BalanceOutboundConnections
Sets the strategy for allocating outbound connections from upstreams across Envoy proxy threads. The only supported value is exact_balance
. By default, no connections are balanced. Refer to the Envoy documentation for details.
- Default: none
- Data type: string
UpstreamConfig.Defaults.Limits
Map that specifies a set of limits to apply to when connecting upstream services. The following table describes limits you can configure:
Limit | Description | Data type | Default |
---|---|---|---|
MaxConnections | Specifies the maximum number of connections a service instance can establish against the upstream. Define this limit for HTTP/1.1 traffic. | integer | 0 |
MaxPendingRequests | Specifies the maximum number of requests that are queued while waiting for a connection to establish. An L7 protocol must be defined in the protocol field for this limit to take effect. | integer | 0 |
MaxConcurrentRequests | Specifies the maximum number of concurrent requests. Define this limit for HTTP/2 traffic. An L7 protocol must be defined in the protocol field for this limit to take effect. | integer | 0 |
UpstreamConfig.Defaults.PassiveHealthCheck
Map that specifies a set of rules that enable Consul to remove hosts from the upstream cluster that are unreachable or that return errors. The following table describes the health check parameters you can configure:
Limit | Description | Data type | Default |
---|---|---|---|
Interval | Specifies the time between checks. | string | 0s |
MaxFailures | Specifies the number of consecutive failures allowed per check interval. If exceeded, Consul removes the host from the load balancer. | integer | 0 |
EnforcingConsecutive5xx | Specifies a percentage that indicates how many times out of 100 that Consul ejects the host when it detects an outlier status. The outlier status is determined by consecutive errors in the 500-599 response range. | integer | 100 |
MaxEjectionPercent | Specifies the maximum percentage of an upstream cluster that Consul ejects when the proxy reports an outlier. Consul ejects at least one host when an outlier is detected regardless of the value. | integer | 10 |
BaseEjectionTime | Specifies the minimum amount of time that an ejected host must remain outside the cluster before rejoining. The real time is equal to the value of the BaseEjectionTime multiplied by the number of times the host has been ejected. | string | 30s |
TransparentProxy
Controls configurations specific to proxies in transparent mode. Refer to Transparent Proxy for additional information.
You can configure the following parameters in the TransparentProxy
block:
Parameter | Description | Data type | Default |
---|---|---|---|
OutboundListenerPort | Specifies the port that the proxy listens on for outbound traffic. This must be the same port number where outbound application traffic is redirected. | integer | 15001 |
DialedDirectly | Enables transparent proxies to dial the proxy instance's IP address directly when set to true . Transparent proxies commonly dial upstreams at the "virtual" tagged address, which load balances across instances. Dialing individual instances can be helpful for stateful services, such as a database cluster with a leader. | boolean | false |
EnvoyExtensions
List of extensions to modify Envoy proxy configuration. Refer to Envoy Extensions for additional information.
You can configure the following parameters in the EnvoyExtensions
block:
Parameter | Description | Data type | Default |
---|---|---|---|
Name | Name of the extension. | string | "" |
Required | When Required is true and the extension does not update any Envoy resources, an error is returned. Use this parameter to ensure that extensions required for secure communication are not unintentionally bypassed. | string | "" |
Arguments | Arguments to pass to the extension executable. | map | nil |
Destination[]
Configures the destination for service traffic through terminating gateways. Refer to Terminating Gateway for additional information.
You can configure the following parameters in the Destination
block:
Parameter | Description | Data type | Default |
---|---|---|---|
Address | Specifies a list of addresses for the destination. You can configure a list of hostnames and IP addresses. Wildcards are not supported. | list | none |
Port | Specifies the port number of the destination. | integer | 0 |
MaxInboundConnections
Specifies the maximum number of concurrent inbound connections to each service instance.
- Default:
0
- Data type: integer
LocalConnectTimeoutMs
Specifies the number of milliseconds allowed for establishing connections to the local application instance before timing out.
- Default:
5000
- Data type: integer
LocalRequestTimeoutMs
Specifies the timeout for HTTP requests to the local application instance. Applies to HTTP-based protocols only. If not specified, inherits the Envoy default for route timeouts.
- Default: Inherits
15s
from Envoy as the default - Data type: string
MeshGateway
Specifies the default mesh gateway mode
field for the service. Refer to Service Mesh Proxy Configuration in the mesh gateway documentation for additional information.
You can specify the following string values for the mode
field:
none
: The service does not make outbound connections through a mesh gateway. Instead, the service makes outbound connections directly to the destination services.local
: The service mesh proxy makes an outbound connection to a gateway running in the same datacenter.remote
: The service mesh proxy makes an outbound connection to a gateway running in the destination datacenter.
ExternalSNI
Specifies the TLS server name indication (SNI) when federating with an external system.
- Default: none
- Data type: string
Expose
Specifies default configurations for exposing HTTP paths through Envoy. Exposing paths through Envoy enables services to listen on localhost only. Applications that are not Consul service mesh-enabled can still contact an HTTP endpoint. Refer to Expose Paths Configuration Reference for additional information and example configurations.
- Default: none
- Data type: map
Expose.Checks
Exposes all HTTP and gRPC checks registered with the agent if set to true
. Envoy exposes listeners for the checks and only accepts connections originating from localhost or Consul's advertise_addr
. The ports for the listeners are dynamically allocated from the agent's expose_min_port
and expose_max_port
configurations.
We recommend enabling the Checks
configuration when a Consul client cannot reach registered services over localhost, such as when Consul agents run in their own pods in Kubernetes.
- Default:
false
- Data type: boolean
Expose.Paths[]
Specifies a list of configuration maps that define paths to expose through Envoy when Expose.Checks
is set to true
. You can configure the following parameters for each map in the list:
Parameter | Description | Data type | Default |
---|---|---|---|
Path | Specifies the HTTP path to expose. You must prepend the path with a forward slash (/ ). | string | none |
LocalPathPort | Specifies the port where the local service listens for connections to the path. | integer | 0 |
ListenPort | Specifies the port where the proxy listens for connections. The port must be available. If the port is unavailable, Envoy does not expose a listener for the path and the proxy registration still succeeds. | integer | 0 |
Protocol | Specifies the protocol of the listener. You can configure one of the following values: http http2 : Use with gRPC traffic | integer | http |
Example configurations
The following examples describe common service-defaults
configurations.
Set the default protocol
In the following example, protocol for the web
service in the default
namespace is set to http
:
Kind = "service-defaults"
Name = "web"
Namespace = "default"
Protocol = "http"
You can also set the global default protocol for all proxies in the proxy-defaults
configuration entry, but the protocol specified for individual service instances in the service-defaults
configuration entry takes precedence over the globally-configured value set in the proxy-defaults
.
Upstream configuration
The following example sets default connection limits and mesh gateway mode across all upstreams of the dashboard
service.
It also overrides the mesh gateway mode used when dialing its counting
upstream service.
Kind = "service-defaults"
Name = "dashboard"
UpstreamConfig = {
Defaults = {
MeshGateway = {
Mode = "local"
}
Limits = {
MaxConnections = 512
MaxPendingRequests = 512
MaxConcurrentRequests = 512
}
}
Overrides = [
{
Name = "counting"
MeshGateway = {
Mode = "remote"
}
}
]
}
Terminating gateway destination
The following examples creates a default destination assigned to a terminating gateway. A destination represents a location outside the Consul cluster. Services can dial destinations dialed directly when transparent proxy mode is enabled.
Kind = "service-defaults"
Name = "test-destination"
Protocol = "tcp"
Destination {
Addresses = ["test.com","test.org"]
Port = 443
}