• HashiCorp Developer

  • HashiCorp Cloud Platform
  • Terraform
  • Packer
  • Consul
  • Vault
  • Boundary
  • Nomad
  • Waypoint
  • Vagrant
Consul
  • Install
  • Tutorials
  • Documentation
  • API
  • CLI
  • Try Cloud(opens in new tab)
  • Sign up
Consul Home

Documentation

Skip to main content
  • Documentation
  • What is Consul?


    • Overview
    • How Service Mesh Works
    • Configuration
      • Overview
      • Ingress Gateway
      • Mesh
      • Exported Services
      • Proxy Defaults
      • Service Defaults
      • Service Intentions
      • Service Resolver
      • Service Router
      • Service Splitter
      • Terminating Gateway
    • Service-to-service permissions - Intentions
    • Service-to-service permissions - Intentions (Legacy Mode)
    • Transparent Proxy
    • Connectivity Tasks
    • Distributed Tracing
    • Nomad
    • Kubernetes
    • Develop and Debug


  • HCP Consul


  • Resources

  • Tutorial Library
  • Certifications
  • Community Forum
    (opens in new tab)
  • Support
    (opens in new tab)
  • GitHub
    (opens in new tab)
  1. Developer
  2. Consul
  3. Documentation
  4. Service Mesh
  5. Configuration Entries
  • Consul
  • v1.13.x
  • v1.12.x
  • v1.11.x
  • v1.10.x
  • v1.9.x
  • v1.8.x

»Configuration Entry Overview

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

The following configuration entries are supported:

  • 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

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

Edit this page on GitHub

On this page

  1. Configuration Entry Overview
  2. Managing Configuration Entries
  3. Using Configuration Entries For Service Defaults
Give Feedback(opens in new tab)
  • Certifications
  • System Status
  • Terms of Use
  • Security
  • Privacy
  • Trademark Policy
  • Trade Controls
  • Give Feedback(opens in new tab)