github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '52cb3ca755'
${ noResults }
consul/website/content/docs/connect/config-entries/index.mdx

55 lines
2.2 KiB
Raw Normal View History Unescape

Move cfg entry docs to under connect from agent (#9533) Since all config entries are currently related to service mesh it's a much more natural place to look for them under Service Mesh than under Agent.
4 years ago
---
layout: docs
page_title: Configuration Entry Definitions
description: >-
Consul allows storing configuration entries centrally to be used as defaults
for configuring other aspects of Consul.
---
# Configuration Entries
Configuration entries can be used to configure the behavior of Consul Connect.
The following configuration entries are supported:
- [Ingress Gateway](/docs/connect/config-entries/ingress-gateway) - defines the
configuration for an ingress gateway
docs: remove name field from Mesh config entry Also document the name of these config entries in the API docs, so that users know how to query for them. And fix the name of mesh on the index page.
4 years ago
- [Mesh](/docs/connect/config-entries/mesh) <sup>Beta</sup> - controls
mesh-wide configuration that applies across namespaces and federated datacenters.
Move cfg entry docs to under connect from agent (#9533) Since all config entries are currently related to service mesh it's a much more natural place to look for them under Service Mesh than under Agent.
4 years ago
- [Proxy Defaults](/docs/connect/config-entries/proxy-defaults) - controls
proxy configuration
- [Service Defaults](/docs/connect/config-entries/service-defaults) - configures
defaults for all the instances of a given service
- [Service Intentions](/docs/connect/config-entries/service-intentions) - defines
the [intentions](/docs/connect/intentions) for a destination service
- [Service Resolver](/docs/connect/config-entries/service-resolver) - matches
service instances with a specific Connect upstream discovery requests
- [Service Router](/docs/connect/config-entries/service-router) - defines
where to send layer 7 traffic based on the HTTP route
- [Service Splitter](/docs/connect/config-entries/service-splitter) - defines
how to divide requests for a single HTTP route based on percentages
- [Terminating Gateway](/docs/connect/config-entries/terminating-gateway) - defines the
services associated with terminating gateway
## Managing Configuration Entries
See [Agent - Config Entries](/docs/agent/config-entries).
## Using Configuration Entries For Service Defaults
Outside of Kubernetes, when the agent is
[configured](/docs/agent/options#enable_central_service_config) 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.