docs: updated connect docs and re-deploying missed changes
This commit is contained in:
parent
e3eab78fb3
commit
7ead9840b5
|
@ -7,29 +7,42 @@ description: >-
|
|||
connections, automatically wrapping and verifying TLS connections.
|
||||
---
|
||||
|
||||
# Connect Configuration
|
||||
# Service Mesh Configuration
|
||||
|
||||
There are many configuration options exposed for Connect. The only option
|
||||
that must be set is the "enabled" option on Consul Servers to enable Connect.
|
||||
There are many configuration options exposed for Consul service mesh. The only option
|
||||
that must be set is the "connect.enabled" option on Consul Servers to enable Consul service mesh.
|
||||
All other configurations are optional and have reasonable defaults.
|
||||
|
||||
-> **Tip:** Connect is enabled by default when running Consul in
|
||||
As a reminder, Consul Connect is used interchangeably
|
||||
with the name Consul Service Mesh and is what this document will use to refer to for Service Mesh functionality within Consul.
|
||||
|
||||
-> **Tip:** Service mesh is enabled by default when running Consul in
|
||||
dev mode with `consul agent -dev`.
|
||||
|
||||
## Agent Configuration
|
||||
|
||||
The first step to use Connect is to enable Connect for your Consul
|
||||
The first step to use service mesh is to enable Connect for your Consul
|
||||
cluster. By default, Connect is disabled. Enabling Connect requires changing
|
||||
the configuration of only your Consul _servers_ (not client agents). To enable
|
||||
Connect, add the following to a new or existing
|
||||
[server configuration file](/docs/agent/config/config-files). In an existing cluster, this configuration change requires a Consul server restart, which you can perform one server at a time to maintain availability. In HCL:
|
||||
|
||||
|
||||
<CodeTabs heading="Enable Consul service mesh" tabs={[ "HCL", "JSON" ]}>
|
||||
|
||||
```hcl
|
||||
connect {
|
||||
enabled = true
|
||||
}
|
||||
```
|
||||
|
||||
```json
|
||||
"connect": {
|
||||
"enabled": true
|
||||
}
|
||||
```
|
||||
</CodeTabs>
|
||||
|
||||
This will enable Connect and configure your Consul cluster to use the
|
||||
built-in certificate authority for creating and managing certificates.
|
||||
You may also configure Consul to use an external
|
||||
|
|
|
@ -6,15 +6,18 @@ description: >-
|
|||
and performance, intention and certificate authority replication.
|
||||
---
|
||||
|
||||
# How Connect Works
|
||||
# How Service Mesh Works
|
||||
|
||||
This page details the inner workings of some of Connect's core features.
|
||||
Understanding how these features work isn't a prerequisite for using Connect,
|
||||
This page details the inner workings of some of Consul sevice mehs's core features.
|
||||
Understanding how these features work isn't a prerequisite for using Consul service mesh,
|
||||
but will help you build a mental model of what's going on under the hood, which
|
||||
may help you reason about Connect's behavior in more complex deployment
|
||||
may help you reason about service mesh's behavior in more complex deployment
|
||||
scenarios.
|
||||
|
||||
To try Connect locally, complete the [Getting Started with Consul service
|
||||
As a reminder, Consul Connect is used interchangeably
|
||||
with the name Consul Service Mesh and is what this document will use to refer to for Service Mesh functionality within Consul.
|
||||
|
||||
To try service mesh locally, complete the [Getting Started with Consul service
|
||||
mesh](https://learn.hashicorp.com/tutorials/consul/service-mesh?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS)
|
||||
tutorial.
|
||||
|
||||
|
|
|
@ -142,7 +142,7 @@
|
|||
"path": "connect"
|
||||
},
|
||||
{
|
||||
"title": "How Connect Works",
|
||||
"title": "How Service Mesh Works",
|
||||
"path": "connect/connect-internals"
|
||||
},
|
||||
{
|
||||
|
|
Loading…
Reference in New Issue