github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
consul/website/content/docs/connect/config-entries/index.mdx

57 lines
2.5 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
docs: consistently name Consul service mesh (#17222) Remove outdated usage of "Consul Connect" instead of Consul service mesh. The connect subsystem in Consul provides Consul's service mesh capabilities. However, the term "Consul Connect" should not be used as an alternative to the name "Consul service mesh".
2023-05-05 17:41:40 +00:00
Configuration entries can be used to configure the behavior of Consul service mesh.
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
The following configuration entries are supported:
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
- [Ingress Gateway](/consul/docs/connect/config-entries/ingress-gateway) - defines the
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 for an ingress gateway
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
- [Mesh](/consul/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
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
- [Exported Services](/consul/docs/connect/config-entries/exported-services) - enables
docs: Small docs updates, peering and K8s CNI (#15702)
2022-12-07 18:08:24 +00:00
Consul to export service instances to other peers or to other admin partitions local or remote to the datacenter.
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
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
- [Proxy Defaults](/consul/docs/connect/config-entries/proxy-defaults) - controls
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 configuration
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
- [Service Defaults](/consul/docs/connect/config-entries/service-defaults) - configures
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
defaults for all the instances of a given service
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
- [Service Intentions](/consul/docs/connect/config-entries/service-intentions) - defines
the [intentions](/consul/docs/connect/intentions) for a destination service
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: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
- [Service Resolver](/consul/docs/connect/config-entries/service-resolver) - matches
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
service instances with a specific Connect upstream discovery requests
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
- [Service Router](/consul/docs/connect/config-entries/service-router) - defines
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
where to send layer 7 traffic based on the HTTP route
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
- [Service Splitter](/consul/docs/connect/config-entries/service-splitter) - defines
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
how to divide requests for a single HTTP route based on percentages
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
- [Terminating Gateway](/consul/docs/connect/config-entries/terminating-gateway) - defines the
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
services associated with terminating gateway
## Managing Configuration Entries
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
See [Agent - Config Entries](/consul/docs/agent/config-entries).
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
## Using Configuration Entries For Service Defaults
Outside of Kubernetes, when the agent is
docs: Migrate link formats (#15976) * Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
2023-01-25 16:52:43 +00:00
[configured](/consul/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.