d447b54ad3
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".
27 lines
985 B
Plaintext
27 lines
985 B
Plaintext
---
|
|
layout: api
|
|
page_title: Connect - HTTP API
|
|
description: >-
|
|
The `/connect` endpoints provide access to service mesh-related operations for
|
|
intentions and the certificate authority.
|
|
---
|
|
|
|
# Connect HTTP Endpoint
|
|
|
|
The `/connect` endpoints provide access to
|
|
[service mesh-related](/consul/docs/connect) operations for
|
|
intentions and the certificate authority.
|
|
|
|
There are also service mesh-related endpoints in the
|
|
[Agent](/consul/api-docs/agent) and [Catalog](/consul/api-docs/catalog) APIs. For example,
|
|
the API for requesting a TLS certificate for a service is part of the agent
|
|
APIs. And the catalog API has an endpoint for finding all mesh-capable
|
|
services in the catalog.
|
|
|
|
The noun _connect_ is used throughout this documentation to refer to the connect
|
|
subsystem that provides Consul's service mesh capabilities.
|
|
Where you encounter the _noun_ connect, it is usually functionality specific to
|
|
service mesh.
|
|
|
|
Please choose a sub-section in the navigation for more information.
|