Configuration Entry Overview

Configuration entries can be used to configure the behavior of Consul service mesh.

The following configuration entries are supported:

• API Gateway - defines the configuration for an API gateway

• Ingress Gateway - defines the configuration for an ingress gateway

• Mesh - controls mesh-wide configuration that applies across namespaces and federated datacenters.

• Exported Services - enables Consul to export service instances to other peers or to other admin partitions local or remote to the datacenter.

• Proxy Defaults - controls proxy configuration

• Sameness Group - defines partitions and cluster peers with identical services

• Service Defaults - configures defaults for all the instances of a given service

• Service Intentions - defines the intentions for a destination service

• Service Resolver - matches service instances with a specific Connect upstream discovery requests

• Service Router - defines where to send layer 7 traffic based on the HTTP route

• Service Splitter - defines how to divide requests for a single HTTP route based on percentages

• Terminating Gateway - defines the services associated with terminating gateway

Managing Configuration Entries

See Agent - Config Entries.

Using Configuration Entries For Service Defaults

Outside of Kubernetes, when the agent is configured to enable central service configurations, it will look for service configuration defaults that match a registering service instance. If it finds any, the agent will merge those defaults with the service instance configuration. This allows for things like service protocol or proxy configuration to be defined globally and inherited by any affected service registrations.