status-im/consul
2
0
Fork 0
mirror of https://github.com/status-im/consul.git synced 2025-01-22 03:29:43 +00:00
Code Issues Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source 
Co-authored-by: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com>
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
Co-authored-by: Luke Kysow <1034429+lkysow@users.noreply.github.com>
This commit is contained in:
Jeff Boruszak 2022-09-15 10:32:23 -05:00 committed by GitHub
parent a208928c2f
commit 2a86195f22
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
16 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/enterprise/backups.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Automated Backups (Enterprise)
description: >-
The automated backup process runs a snapshot agent and saves backup files to a cloud storage provider so that you can restore Consul servers. Supported providers include: Amazon S3, Google Cloud Storage, and Azure Blob Storage.
Learn about launching the snapshot agent to automatically backup files to a cloud storage provider so that you can restore Consul servers. Supported providers include: Amazon S3, Google Cloud Storage, and Azure Blob Storage.
---
# Automated Backups

4
website/content/docs/enterprise/federation.mdx
View File

@ -1,8 +1,8 @@
---
layout: docs
page_title: Advanced Federation (Enterprise)
page_title: Federated Network Areas (Enterprise)
description: >-
Advanced federation connects partial network areas through paired servers. Learn how to support hub-and-spoke and tree network topologies in your Consul deployment.
Network areas connect individual datacenters in a WAN federation, providing an alternative to connecting every datacenter. Learn how to support hub-and-spoke network topologies in a WAN federated Consul deployment.
---
# Consul Enterprise Advanced Federation

2
website/content/docs/enterprise/index.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Consul Enterprise
description: >-
Consul Enterprise is a paid offering that adds features to support large and complex deployments. Learn how Enterprise can help you scale infrastructure, simplify operations, and make networks more resilient.
Consul Enterprise is a paid offering that extends Consul’s open source functions to support large and complex deployments. Learn about scaling infrastructure, simplifying operations, and making networks more resilient with Enterprise.
---
# Consul Enterprise

2
website/content/docs/enterprise/license/overview.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Enterprise Licenses
description: >-
Consul server, client, and snapshot agents require a license in order to use Enterprise features. Learn how to apply licenses to environment variables and configuration files.
Consul Enterprise server, client, and snapshot agents require a license on startup in order to use Enterprise features. Learn how to apply licenses using environment variables or configuration files.
---
# Consul Enterprise License

2
website/content/docs/enterprise/network-segments.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Network Segments (Enterprise)
description: >-
Network segments enable gossip in a datacenter when network rules or firewalls prevent clients from communicating directly. Learn how to configure server and client agents to use segmented networks.
Network segments enable LAN gossip in a datacenter when network rules or firewalls prevent specific sets of clients from communicating directly. Learn about configuring server and client agents to operate in segmented networks.
---
# Network Segments

2
website/content/docs/enterprise/read-scale.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Read Replicas (Enterprise)
description: >-
Learn how you can add non-voting servers to clusters as read replicas to provide enhanced read scalability without impacting write latency.
Learn how you can add non-voting servers to datacenters as read replicas to provide enhanced read scalability without impacting write latency.
---
# Enhanced Read Scalability with Read Replicas

2
website/content/docs/enterprise/redundancy.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Redundancy Zones (Enterprise)
description: >-
Add non-voting servers to clusters to create redundancy zones for deployments. Learn how distributed ""hot standby"" servers improve resiliency and scaling by preserving quorum.
Redundancy zones are regions of a cluster containing "hot standby" servers, or non-voting servers that can replace voting servers in the event of a failure. Learn about redundancy zones and how they improve resiliency and increase fault tolerance without affecting latency.
---
# Redundancy Zones

2
website/content/docs/enterprise/sentinel.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Sentinel in Consul (Enterprise)
description: >-
Sentinel is a framework and language for creating logic-based policies. Learn how Consul can use Sentinel policies to extend the ACL system's capabilities.
Sentinel is an access-control-policy-as-code framework and language. Learn how Consul can use Sentinel policies to extend the ACL system's capabilities and further secure your clusters by controlling key-value (KV) store write access.
---
# Sentinel in Consul

2
website/content/docs/enterprise/upgrades.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Automated Upgrades (Enterprise)
description: >-
Automated upgrades simplify the process for updating Consul. Learn how Consul can deploy a new version on additional servers and then automatically remove outdated versions without server downtime.
Automated upgrades simplify the process for updating Consul. Learn how Consul can gracefully transition from existing server agents to a new set of server agents without Consul downtime.
---
# Automated Upgrades

2
website/content/docs/install/bootstrapping.mdx
View File

@ -5,7 +5,7 @@ description: >-
Bootstrapping a datacenter is the initial deployment process in Consul that starts server agents and joins them together. Learn how to automatically or manually join servers in a cluster.
---
# Bootstrapping a Datacenter
# Bootstrap a Datacenter
An agent can run in either client or server mode. Server nodes are responsible for running the
[consensus protocol](/docs/architecture/consensus) and storing the cluster state.

2
website/content/docs/install/cloud-auto-join.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Auto-join a Cloud Provider
description: >-
Configure servers to auto-join clusters on startup. Use the CLI or an agent configuration file to specify either an IP address or a cloud provider for the server to join.
Auto-join enables agents to automatically join other agents running in the cloud. To configure auto-join, specify agent addresses with compute node metadata for the cloud provider instead of an IP address. Use the CLI or an agent configuration file to configure cloud auto-join.
---
# Cloud Auto-join

2
website/content/docs/install/index.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Install Consul
description: >-
Install Consul to get started with service discovery and service mesh. Follow the installation instructions to download the precompiled binary, or use Go to compile from the source manually.
Install Consul to get started with service discovery and service mesh. Follow the installation instructions to download the precompiled binary, or use Go to compile from source.
---
# Install Consul

2
website/content/docs/install/manual-bootstrap.mdx
View File

@ -2,7 +2,7 @@
layout: docs
page_title: Manually Bootstrap a Datacenter
description: >-
Manually bootstrap a datacenter to deploy your Consul servers and join them together for the first time. As of Consul v0.4, automatic bootstrapping is recommended instead.
Manually bootstrap a datacenter to deploy your Consul servers and join them together for the first time. For Consul v0.4+, we recommend automatic bootstrapping instead.
---
# Manually Bootstrapping a Datacenter

4
website/content/docs/install/performance.mdx
View File

@ -1,8 +1,8 @@
---
layout: docs
page_title: Server Requirements
page_title: Server Performance Requirements
description: >-
Consul servers require computing resources to communicate and process data quickly. Learn about Consul's minimum server requirements and recommendations for different workloads.
Consul servers require sufficient compute resources to communicate and process data quickly. Learn about Consul's minimum server requirements and recommendations for different workloads.
---
# Server Performance

4
website/content/docs/install/ports.mdx
View File

@ -1,8 +1,8 @@
---
layout: docs
page_title: Port Requirements
page_title: Required Ports
description: >-
Consul requires bind ports for directing DNS, HTTP, gRPC, Serf, and proxy requests. Learn about these reserved ports and how Consul uses them for specific communication functions.
Consul requires multiple ports for directing DNS, HTTP, gRPC, gossip, and sidecar proxy requests. Learn about required and optional ports, and how Consul uses them for specific communication functions.
---
# Required Ports

2
website/content/docs/troubleshoot/common-errors.mdx
View File

@ -1,6 +1,6 @@
---
layout: docs
page_title: Common Error Messages | Troubleshoot
page_title: Common Error Messages - Troubleshoot
description: >-
Troubleshoot issues based on the error message. Common errors result from failed actions, timeouts, multiple entries, bad and expired certificates, invalid characters, syntax parsing, malformed responses, and exceeded deadlines.
---