luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-consul/website/content/docs/connect/config-entries/index.mdx

57 lines
2.4 KiB
Plaintext
Raw Normal View History

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.
2021-01-13 20:48:48 +00:00
---
layout: docs
/docs/connect/config-entries
2022-09-13 21:04:13 +00:00
page_title: Configuration Entry Overview
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.
2021-01-13 20:48:48 +00:00
description: >-
Spacing and title fixes
2022-09-16 15:28:32 +00:00
Configuration entries define service mesh behaviors in order to secure and manage traffic. Learn about Consul’s different config entry kinds and get links to configuration reference pages.
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.
2021-01-13 20:48:48 +00:00
---
/docs/connect/config-entries
2022-09-13 21:04:13 +00:00
# Configuration Entry Overview
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.
2021-01-13 20:48:48 +00:00
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 beta tag for 1.10 features Remove beta tag for 1.10 features which are now GA.
2021-06-22 22:04:50 +00:00
- [Mesh](/docs/connect/config-entries/mesh) - controls
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.
2021-05-04 21:32:07 +00:00
mesh-wide configuration that applies across namespaces and federated datacenters.
docs: add exported services to overview
2021-12-17 04:20:11 +00:00
- [Exported Services](/docs/connect/config-entries/exported-services) <EnterpriseAlert inline /> - enables
Consul to export service instances to other admin partitions.
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.
2021-05-04 21:32:07 +00:00
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.
2021-01-13 20:48:48 +00:00
- [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
docs: simplify agent docs slugs
2022-01-11 01:30:50 +00:00
[configured](/docs/agent/config/config-files#enable_central_service_config) to enable
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.
2021-01-13 20:48:48 +00:00
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.