Browse Source

Merge pull request #11879 from hashicorp/david-yu-exported-services

docs: add Exported Services to overview
pull/11881/head
mrspanishviking 3 years ago committed by GitHub
parent
commit
dd1179177f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 4
      website/content/docs/connect/config-entries/exported-services.mdx
  2. 3
      website/content/docs/connect/config-entries/index.mdx

4
website/content/docs/connect/config-entries/exported-services.mdx

@ -6,11 +6,11 @@ description: >-
Settings in this configuration entry can apply to services in any namespace of the specified partition. Write access to the mesh resource is required.
---
# Exported Services
# Exported Services <EnterpriseAlert inline />
This topic describes the `exported-services` configuration entry type. The `exported-services` configuration entry enables Consul to export service instances to other admin partitions from a single file. This enables your services to be networked across admin partitions. See [Admin Partitions](/docs/enterprise/admin-partitions) for additional information.
-> **v1.11.0+:** This config entry is supported in Consul versions 1.11.0+.
-> **v1.11.0+:** This config entry is supported in Consul Enterprise versions 1.11.0+.
## Introduction

3
website/content/docs/connect/config-entries/index.mdx

@ -17,6 +17,9 @@ The following configuration entries are supported:
- [Mesh](/docs/connect/config-entries/mesh) - controls
mesh-wide configuration that applies across namespaces and federated datacenters.
- [Exported Services](/docs/connect/config-entries/exported-services) <EnterpriseAlert inline /> - enables
Consul to export service instances to other admin partitions.
- [Proxy Defaults](/docs/connect/config-entries/proxy-defaults) - controls
proxy configuration

Loading…
Cancel
Save