From ace98ca90d7541d8b67d5a5763f08e8999933098 Mon Sep 17 00:00:00 2001 From: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> Date: Fri, 16 Sep 2022 11:31:14 -0500 Subject: [PATCH] Merge pull request #14656 from hashicorp/docs/search-metadata-headers docs: Search Refresh Fixes --- website/content/docs/agent/config-entries.mdx | 2 +- website/content/docs/agent/config/cli-flags.mdx | 4 ++-- website/content/docs/agent/config/index.mdx | 4 ++-- website/content/docs/agent/index.mdx | 2 +- website/content/docs/agent/options.mdx | 4 ++-- website/content/docs/agent/rpc.mdx | 2 +- website/content/docs/agent/sentinel.mdx | 2 +- website/content/docs/agent/telemetry.mdx | 4 ++-- website/content/docs/architecture/anti-entropy.mdx | 2 +- website/content/docs/architecture/consensus.mdx | 2 +- website/content/docs/architecture/coordinates.mdx | 2 +- website/content/docs/architecture/gossip.mdx | 2 +- .../content/docs/architecture/improving-consul-resilience.mdx | 2 +- website/content/docs/architecture/index.mdx | 2 +- website/content/docs/architecture/jepsen.mdx | 2 +- website/content/docs/connect/ca/aws.mdx | 4 ++-- website/content/docs/connect/ca/consul.mdx | 4 ++-- website/content/docs/connect/ca/index.mdx | 4 ++-- website/content/docs/connect/ca/vault.mdx | 4 ++-- .../docs/connect/cluster-peering/create-manage-peering.mdx | 4 ++-- website/content/docs/connect/cluster-peering/index.mdx | 4 ++-- website/content/docs/connect/cluster-peering/k8s.mdx | 2 +- .../content/docs/connect/config-entries/exported-services.mdx | 4 ++-- website/content/docs/connect/config-entries/index.mdx | 2 +- .../content/docs/connect/config-entries/ingress-gateway.mdx | 4 ++-- website/content/docs/connect/config-entries/mesh.mdx | 4 ++-- .../content/docs/connect/config-entries/proxy-defaults.mdx | 4 ++-- .../content/docs/connect/config-entries/service-defaults.mdx | 4 ++-- .../docs/connect/config-entries/service-intentions.mdx | 4 ++-- .../content/docs/connect/config-entries/service-resolver.mdx | 4 ++-- .../content/docs/connect/config-entries/service-router.mdx | 4 ++-- .../content/docs/connect/config-entries/service-splitter.mdx | 4 ++-- .../docs/connect/config-entries/terminating-gateway.mdx | 4 ++-- website/content/docs/connect/configuration.mdx | 4 ++-- website/content/docs/connect/connect-internals.mdx | 4 ++-- website/content/docs/connect/connectivity-tasks.mdx | 2 +- website/content/docs/connect/dev.mdx | 2 +- website/content/docs/connect/distributed-tracing.mdx | 2 +- website/content/docs/connect/gateways/index.mdx | 2 +- website/content/docs/connect/gateways/ingress-gateway.mdx | 2 +- .../mesh-gateway/service-to-service-traffic-datacenters.mdx | 2 +- .../mesh-gateway/service-to-service-traffic-partitions.mdx | 2 +- .../mesh-gateway/service-to-service-traffic-peers.mdx | 2 +- .../mesh-gateway/wan-federation-via-mesh-gateways.mdx | 2 +- website/content/docs/connect/gateways/terminating-gateway.mdx | 2 +- website/content/docs/connect/index.mdx | 2 +- website/content/docs/connect/intentions-legacy.mdx | 2 +- website/content/docs/connect/intentions.mdx | 2 +- website/content/docs/connect/l7-traffic/discovery-chain.mdx | 4 ++-- website/content/docs/connect/l7-traffic/index.mdx | 4 ++-- website/content/docs/connect/native/go.mdx | 4 ++-- website/content/docs/connect/native/index.mdx | 4 ++-- website/content/docs/connect/nomad.mdx | 4 ++-- website/content/docs/connect/observability/index.mdx | 4 ++-- .../content/docs/connect/observability/ui-visualization.mdx | 4 ++-- website/content/docs/connect/proxies/built-in.mdx | 2 +- website/content/docs/connect/proxies/envoy.mdx | 2 +- website/content/docs/connect/proxies/index.mdx | 2 +- website/content/docs/connect/proxies/integrate.mdx | 2 +- website/content/docs/connect/proxies/managed-deprecated.mdx | 2 +- website/content/docs/connect/registration/index.mdx | 2 +- .../docs/connect/registration/service-registration.mdx | 2 +- website/content/docs/connect/registration/sidecar-service.mdx | 2 +- website/content/docs/connect/security.mdx | 4 ++-- website/content/docs/connect/transparent-proxy.mdx | 4 ++-- website/content/docs/discovery/checks.mdx | 2 +- website/content/docs/discovery/dns.mdx | 2 +- website/content/docs/discovery/services.mdx | 2 +- website/content/docs/download-tools.mdx | 2 +- website/content/docs/enterprise/admin-partitions.mdx | 2 +- website/content/docs/enterprise/audit-logging.mdx | 2 +- website/content/docs/enterprise/backups.mdx | 2 +- website/content/docs/enterprise/federation.mdx | 2 +- website/content/docs/enterprise/index.mdx | 2 +- website/content/docs/enterprise/license/faq.mdx | 2 +- website/content/docs/enterprise/license/overview.mdx | 2 +- website/content/docs/enterprise/namespaces.mdx | 2 +- website/content/docs/enterprise/network-segments.mdx | 2 +- website/content/docs/enterprise/read-scale.mdx | 2 +- website/content/docs/enterprise/redundancy.mdx | 2 +- website/content/docs/enterprise/sentinel.mdx | 2 +- website/content/docs/enterprise/upgrades.mdx | 2 +- website/content/docs/install/bootstrapping.mdx | 2 +- website/content/docs/install/cloud-auto-join.mdx | 2 +- website/content/docs/install/glossary.mdx | 2 +- website/content/docs/install/index.mdx | 2 +- website/content/docs/install/manual-bootstrap.mdx | 2 +- website/content/docs/install/performance.mdx | 2 +- website/content/docs/install/ports.mdx | 2 +- website/content/docs/integrate/nia-integration.mdx | 2 +- website/content/docs/integrate/partnerships.mdx | 2 +- website/content/docs/internals/index.mdx | 2 +- .../content/docs/intro/usecases/what-is-a-service-mesh.mdx | 2 +- .../content/docs/intro/usecases/what-is-service-discovery.mdx | 2 +- website/content/docs/k8s/annotations-and-labels.mdx | 2 +- website/content/docs/k8s/architecture.mdx | 2 +- website/content/docs/k8s/compatibility.mdx | 2 +- website/content/docs/k8s/connect/connect-ca-provider.mdx | 2 +- website/content/docs/k8s/connect/health.mdx | 2 +- website/content/docs/k8s/connect/index.mdx | 2 +- website/content/docs/k8s/connect/ingress-controllers.mdx | 2 +- website/content/docs/k8s/connect/ingress-gateways.mdx | 2 +- website/content/docs/k8s/connect/observability/metrics.mdx | 2 +- website/content/docs/k8s/connect/terminating-gateways.mdx | 2 +- website/content/docs/k8s/crds/index.mdx | 2 +- website/content/docs/k8s/crds/upgrade-to-crds.mdx | 2 +- website/content/docs/k8s/dns.mdx | 2 +- website/content/docs/k8s/helm.mdx | 2 +- website/content/docs/k8s/index.mdx | 2 +- website/content/docs/k8s/installation/install-cli.mdx | 2 +- website/content/docs/k8s/installation/install.mdx | 2 +- .../k8s/installation/platforms/self-hosted-kubernetes.mdx | 2 +- website/content/docs/k8s/k8s-cli.mdx | 2 +- website/content/docs/k8s/operations/certificate-rotation.mdx | 2 +- .../docs/k8s/operations/gossip-encryption-key-rotation.mdx | 2 +- .../content/docs/k8s/operations/tls-on-existing-cluster.mdx | 2 +- website/content/docs/k8s/operations/uninstall.mdx | 2 +- website/content/docs/k8s/service-sync.mdx | 2 +- website/content/docs/k8s/upgrade/index.mdx | 2 +- website/content/docs/k8s/upgrade/upgrade-cli.mdx | 2 +- .../content/docs/security/acl/acl-federated-datacenters.mdx | 2 +- website/content/docs/security/acl/acl-legacy.mdx | 2 +- website/content/docs/security/acl/acl-migrate-tokens.mdx | 2 +- website/content/docs/security/acl/acl-policies.mdx | 2 +- website/content/docs/security/acl/acl-roles.mdx | 2 +- website/content/docs/security/acl/acl-rules.mdx | 2 +- website/content/docs/security/acl/acl-tokens.mdx | 2 +- website/content/docs/security/acl/index.mdx | 4 ++-- website/content/docs/security/encryption.mdx | 2 +- website/content/docs/security/index.mdx | 4 ++-- website/content/docs/security/security-models/core.mdx | 4 ++-- website/content/docs/security/security-models/index.mdx | 4 ++-- website/content/docs/security/security-models/nia.mdx | 4 ++-- website/content/docs/troubleshoot/common-errors.mdx | 2 +- website/content/docs/troubleshoot/faq.mdx | 2 +- 135 files changed, 171 insertions(+), 171 deletions(-) diff --git a/website/content/docs/agent/config-entries.mdx b/website/content/docs/agent/config-entries.mdx index 342337cac259..d3cad1b6a7bf 100644 --- a/website/content/docs/agent/config-entries.mdx +++ b/website/content/docs/agent/config-entries.mdx @@ -2,7 +2,7 @@ layout: docs page_title: How to Use Configuration Entries description: >- -Configuration entries define the behavior of Consul service mesh components. Learn how to use the `consul config` command to create, manage, and delete configuration entries. + Configuration entries define the behavior of Consul service mesh components. Learn how to use the `consul config` command to create, manage, and delete configuration entries. --- # How to Use Configuration Entries diff --git a/website/content/docs/agent/config/cli-flags.mdx b/website/content/docs/agent/config/cli-flags.mdx index c29b93fd503c..8c480778d90d 100644 --- a/website/content/docs/agent/config/cli-flags.mdx +++ b/website/content/docs/agent/config/cli-flags.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Agents: CLI Reference +page_title: Agents - CLI Reference description: >- -Add flags to the `consul agent` command to configure agent properties and actions from the CLI. Learn about configurable options and how to format them with examples. + Add flags to the `consul agent` command to configure agent properties and actions from the CLI. Learn about configurable options and how to format them with examples. --- # Agents Command-line Reference ((#commandline_options)) diff --git a/website/content/docs/agent/config/index.mdx b/website/content/docs/agent/config/index.mdx index e1832d7bbf32..cf54796fa1fe 100644 --- a/website/content/docs/agent/config/index.mdx +++ b/website/content/docs/agent/config/index.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Agents: Configuration Explained +page_title: Agents - Configuration Explained description: >- -Agent configuration is the process of defining server and client agent properties with CLI flags and configuration files. Learn what properties can be configured on reload and how Consul sets precedence for configuration settings. + Agent configuration is the process of defining server and client agent properties with CLI flags and configuration files. Learn what properties can be configured on reload and how Consul sets precedence for configuration settings. --- # Agent Configuration diff --git a/website/content/docs/agent/index.mdx b/website/content/docs/agent/index.mdx index dd070248b229..d70999cfd57d 100644 --- a/website/content/docs/agent/index.mdx +++ b/website/content/docs/agent/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Agents Overview description: >- -Agents maintain register services, respond to queries, maintain datacenter membership information, and make most of Consul’s functions possible. Learn how to start, stop, and configure agents, as well as their requirements and lifecycle. + Agents maintain register services, respond to queries, maintain datacenter membership information, and make most of Consul’s functions possible. Learn how to start, stop, and configure agents, as well as their requirements and lifecycle. --- # Agents Overview diff --git a/website/content/docs/agent/options.mdx b/website/content/docs/agent/options.mdx index f8a66ba3a32c..c135b585e85f 100644 --- a/website/content/docs/agent/options.mdx +++ b/website/content/docs/agent/options.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Agents: Configuration File Reference +page_title: Agents - Configuration File Reference description: >- -Use agent configuration files to assign attributes to agents and configure multiple agents at once. Learn about agent configuration file parameters and formatting with this reference page and sample code. + Use agent configuration files to assign attributes to agents and configure multiple agents at once. Learn about agent configuration file parameters and formatting with this reference page and sample code. --- # Configuration diff --git a/website/content/docs/agent/rpc.mdx b/website/content/docs/agent/rpc.mdx index 5f37606781cf..ecc187a889bf 100644 --- a/website/content/docs/agent/rpc.mdx +++ b/website/content/docs/agent/rpc.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Legacy RPC Protocol description: >- -Consul agents originally could be controlled through the RPC protocol. This feature was deprecated in version 0.8 in favor of the HTTP API. Learn about agent RPC interactions and how they worked. + Consul agents originally could be controlled through the RPC protocol. This feature was deprecated in version 0.8 in favor of the HTTP API. Learn about agent RPC interactions and how they worked. --- # RPC Protocol diff --git a/website/content/docs/agent/sentinel.mdx b/website/content/docs/agent/sentinel.mdx index b44d5bdb2681..d5602d3438bd 100644 --- a/website/content/docs/agent/sentinel.mdx +++ b/website/content/docs/agent/sentinel.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Sentinel ACL Policies (Enterprise) description: >- -Sentinel allows you to include conditional logic in access control policies. Learn how Consul can use Sentinel policies to extend the ACL system's capabilities for controlling key-value (KV) write access. + Sentinel allows you to include conditional logic in access control policies. Learn how Consul can use Sentinel policies to extend the ACL system's capabilities for controlling key-value (KV) write access. --- # Sentinel for KV ACL Policy Enforcement diff --git a/website/content/docs/agent/telemetry.mdx b/website/content/docs/agent/telemetry.mdx index ee81513b57f6..972b01416243 100644 --- a/website/content/docs/agent/telemetry.mdx +++ b/website/content/docs/agent/telemetry.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Agents: Enable Metrics +page_title: Agents - Enable Telemetry Metrics description: >- -Configure agent telemetry to collect operations metrics you can use to debug and observe Consul behavior and performance. Learn about configuration options, the metrics you can collect, and why they're important. + Configure agent telemetry to collect operations metrics you can use to debug and observe Consul behavior and performance. Learn about configuration options, the metrics you can collect, and why they're important. --- # Agent Telemetry diff --git a/website/content/docs/architecture/anti-entropy.mdx b/website/content/docs/architecture/anti-entropy.mdx index 40cceb7f3b19..1ac3d2ba992e 100644 --- a/website/content/docs/architecture/anti-entropy.mdx +++ b/website/content/docs/architecture/anti-entropy.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Anti-Entropy Enforcement description: >- -Anti-entropy keeps distributed systems consistent. Learn how Consul uses an anti-entropy mechanism to periodically sync agent states with the service catalog to prevent the catalog from becoming stale. + Anti-entropy keeps distributed systems consistent. Learn how Consul uses an anti-entropy mechanism to periodically sync agent states with the service catalog to prevent the catalog from becoming stale. --- # Anti-Entropy Enforcement diff --git a/website/content/docs/architecture/consensus.mdx b/website/content/docs/architecture/consensus.mdx index d1525cce4817..f2b5c923ce03 100644 --- a/website/content/docs/architecture/consensus.mdx +++ b/website/content/docs/architecture/consensus.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Consensus Protocol | Raft description: >- -Consul ensures a consistent state using the Raft protocol. A quorum, or a majority of server agents with one leader, agree to state changes before committing to the state log. Learn how Raft works in Consul to ensure state consistency and how that state can be read with different consistency modes to balance read latency and consistency. + Consul ensures a consistent state using the Raft protocol. A quorum, or a majority of server agents with one leader, agree to state changes before committing to the state log. Learn how Raft works in Consul to ensure state consistency and how that state can be read with different consistency modes to balance read latency and consistency. --- # Consensus Protocol diff --git a/website/content/docs/architecture/coordinates.mdx b/website/content/docs/architecture/coordinates.mdx index e70e55f4112e..55fa8850eeff 100644 --- a/website/content/docs/architecture/coordinates.mdx +++ b/website/content/docs/architecture/coordinates.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Network Coordinates description: >- -Network coordinates are node locations in network tomography used to estimate round trip time (RTT). Learn how network coordinates manifest in Consul, how it calculates RTT, and how to work with coordinates to sort catalog information by nearness to a given node. + Network coordinates are node locations in network tomography used to estimate round trip time (RTT). Learn how network coordinates manifest in Consul, how it calculates RTT, and how to work with coordinates to sort catalog information by nearness to a given node. --- # Network Coordinates diff --git a/website/content/docs/architecture/gossip.mdx b/website/content/docs/architecture/gossip.mdx index 4fdab2f75bce..09f85b19bd5c 100644 --- a/website/content/docs/architecture/gossip.mdx +++ b/website/content/docs/architecture/gossip.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Gossip Protocol | Serf description: >- -Consul agents manage membership in datacenters and WAN federations using the Serf protocol. Learn about the differences between LAN and WAN gossip pools and how `serfHealth` affects health checks. + Consul agents manage membership in datacenters and WAN federations using the Serf protocol. Learn about the differences between LAN and WAN gossip pools and how `serfHealth` affects health checks. --- # Gossip Protocol diff --git a/website/content/docs/architecture/improving-consul-resilience.mdx b/website/content/docs/architecture/improving-consul-resilience.mdx index cd59893c873a..960db8a492c4 100644 --- a/website/content/docs/architecture/improving-consul-resilience.mdx +++ b/website/content/docs/architecture/improving-consul-resilience.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Fault Tolerance in Consul description: >- -Fault tolerance is a system's ability to operate without interruption despite component failure. Learn how a set of Consul servers provide fault tolerance through use of a quorum, and how to further improve control plane resilience through use of infrastructure zones and Enterprise redundancy zones. + Fault tolerance is a system's ability to operate without interruption despite component failure. Learn how a set of Consul servers provide fault tolerance through use of a quorum, and how to further improve control plane resilience through use of infrastructure zones and Enterprise redundancy zones. --- # Fault Tolerance diff --git a/website/content/docs/architecture/index.mdx b/website/content/docs/architecture/index.mdx index 79dafd754e84..9b2d13a43cbe 100644 --- a/website/content/docs/architecture/index.mdx +++ b/website/content/docs/architecture/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Consul Architecture description: >- -Consul datacenters consist of clusters of server agents (control plane) and client agents deployed alongside service instances (dataplane). Learn how these components and their different communication methods make Consul possible. + Consul datacenters consist of clusters of server agents (control plane) and client agents deployed alongside service instances (dataplane). Learn how these components and their different communication methods make Consul possible. --- # Consul Internals Overview diff --git a/website/content/docs/architecture/jepsen.mdx b/website/content/docs/architecture/jepsen.mdx index b03a1722078f..44a433c8d35b 100644 --- a/website/content/docs/architecture/jepsen.mdx +++ b/website/content/docs/architecture/jepsen.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Consistency Verification | Jepsen Testing Results description: >- -Jepsen is a tool to measure the reliability and consistency of distributed systems across network partitions. Learn about the Jepsen testing performed on Consul to ensure it gracefully recovers from partitions and maintains consistent state. + Jepsen is a tool to measure the reliability and consistency of distributed systems across network partitions. Learn about the Jepsen testing performed on Consul to ensure it gracefully recovers from partitions and maintains consistent state. --- # Jepsen Testing Results diff --git a/website/content/docs/connect/ca/aws.mdx b/website/content/docs/connect/ca/aws.mdx index 123fe9620def..731d6d7a13ad 100644 --- a/website/content/docs/connect/ca/aws.mdx +++ b/website/content/docs/connect/ca/aws.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Certificate Authority: AWS Certificate Manager +page_title: Service Mesh Certificate Authority - AWS Certificate Manager description: >- -You can use the AWS Certificate Manager Private Certificate Authority as the Consul service mesh's certificate authority to secure your service mesh. Learn how to configure the AWS ACM Private CA, its limitations in Consul, and cost planning considerations. + You can use the AWS Certificate Manager Private Certificate Authority as the Consul service mesh's certificate authority to secure your service mesh. Learn how to configure the AWS ACM Private CA, its limitations in Consul, and cost planning considerations. --- # AWS Certificate Manager as a Service Mesh Certificate Authority diff --git a/website/content/docs/connect/ca/consul.mdx b/website/content/docs/connect/ca/consul.mdx index 389a53166a2c..e861f2f2639c 100644 --- a/website/content/docs/connect/ca/consul.mdx +++ b/website/content/docs/connect/ca/consul.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Certificate Authority: Built-in Service Mesh CA +page_title: Certificate Authority - Built-in Service Mesh CA description: >- -Consul has a built-in service mesh certificate authority that can be used to secure your service mesh without needing a separate CA system. Learn how to configure the built-in service mesh CA as a root CA or an intermediate CA connected to an existing PKI system. + Consul has a built-in service mesh certificate authority that can be used to secure your service mesh without needing a separate CA system. Learn how to configure the built-in service mesh CA as a root CA or an intermediate CA connected to an existing PKI system. --- # Built-In Certificate Authority for Service Mesh diff --git a/website/content/docs/connect/ca/index.mdx b/website/content/docs/connect/ca/index.mdx index 341022707db4..f5efc83b7334 100644 --- a/website/content/docs/connect/ca/index.mdx +++ b/website/content/docs/connect/ca/index.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Certificate Authority: Overview +page_title: Service Mesh Certificate Authority - Overview description: >- -Consul uses a certificate authority (CA) to generate, use, manage, sign, and store certificates for your service mesh. Learn about certificate management, including configuration, root cert rotation, cross-signing, and regenerating the CA. + Consul uses a certificate authority (CA) to generate, use, manage, sign, and store certificates for your service mesh. Learn about certificate management, including configuration, root cert rotation, cross-signing, and regenerating the CA. --- # Service Mesh Certificate Authority Overview diff --git a/website/content/docs/connect/ca/vault.mdx b/website/content/docs/connect/ca/vault.mdx index cb8d666a50fe..f4742da77d5b 100644 --- a/website/content/docs/connect/ca/vault.mdx +++ b/website/content/docs/connect/ca/vault.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Certificate Authority: Vault +page_title: Service Mesh Certificate Authority - Vault description: >- -You can use a Vault PKI secrets engine as the Consul service mesh's certificate authority to secure your service mesh. Learn how to configure the Vault CA as a root CA or an intermediate CA connected to an existing PKI system, and how to manage PKI paths with either Vault or Consul. + You can use a Vault PKI secrets engine as the Consul service mesh's certificate authority to secure your service mesh. Learn how to configure the Vault CA as a root CA or an intermediate CA connected to an existing PKI system, and how to manage PKI paths with either Vault or Consul. --- # Vault as a Service Mesh Certificate Authority diff --git a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx index 595021405b19..56a0ee2ef918 100644 --- a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx +++ b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Cluster Peering: Create and Manage Connections +page_title: Cluster Peering - Create and Manage Connections description: >- -Generate a peering token to establish communication, export services, and authorize requests for cluster peering connections. Learn how to create, list, read, check, and delete peering connections. + Generate a peering token to establish communication, export services, and authorize requests for cluster peering connections. Learn how to create, list, read, check, and delete peering connections. --- # Create and Manage Cluster Peering Connections diff --git a/website/content/docs/connect/cluster-peering/index.mdx b/website/content/docs/connect/cluster-peering/index.mdx index 7526d7b25ec2..f216fb780c2a 100644 --- a/website/content/docs/connect/cluster-peering/index.mdx +++ b/website/content/docs/connect/cluster-peering/index.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh: What is Cluster Peering? +page_title: Service Mesh - What is Cluster Peering? description: >- -Cluster peering establishes communication between independent clusters in Consul, allowing services to interact across datacenters. Learn about the cluster peering process, differences with WAN federation for multi-datacenter deployments, and technical constraints. + Cluster peering establishes communication between independent clusters in Consul, allowing services to interact across datacenters. Learn about the cluster peering process, differences with WAN federation for multi-datacenter deployments, and technical constraints. --- # What is Cluster Peering? diff --git a/website/content/docs/connect/cluster-peering/k8s.mdx b/website/content/docs/connect/cluster-peering/k8s.mdx index 16f87879b86f..c12c7774d23a 100644 --- a/website/content/docs/connect/cluster-peering/k8s.mdx +++ b/website/content/docs/connect/cluster-peering/k8s.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Cluster Peering on Kubernetes description: >- -If you use Consul on Kubernetes, learn how to enable cluster peering, create peering CRDs, and then manage peering connections in consul-k8s. + If you use Consul on Kubernetes, learn how to enable cluster peering, create peering CRDs, and then manage peering connections in consul-k8s. --- # Cluster Peering on Kubernetes diff --git a/website/content/docs/connect/config-entries/exported-services.mdx b/website/content/docs/connect/config-entries/exported-services.mdx index 0c54ba54566d..49e7121b5d55 100644 --- a/website/content/docs/connect/config-entries/exported-services.mdx +++ b/website/content/docs/connect/config-entries/exported-services.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Exported Services: Configuration Entry Reference +page_title: Exported Services - Configuration Entry Reference description: >- -An exported services configuration entry defines the availability of a cluster's services to cluster peers and local admin partitions. Learn about `"exported-services"` config entry parameters and exporting services to other datacenters. + An exported services configuration entry defines the availability of a cluster's services to cluster peers and local admin partitions. Learn about `""exported-services""` config entry parameters and exporting services to other datacenters. --- # Exported Services Configuration Entry diff --git a/website/content/docs/connect/config-entries/index.mdx b/website/content/docs/connect/config-entries/index.mdx index 21e18aaf6752..6ac56fe37b64 100644 --- a/website/content/docs/connect/config-entries/index.mdx +++ b/website/content/docs/connect/config-entries/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Configuration Entry Overview description: >- -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. + 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. --- # Configuration Entry Overview diff --git a/website/content/docs/connect/config-entries/ingress-gateway.mdx b/website/content/docs/connect/config-entries/ingress-gateway.mdx index 48cba230bb2f..b1f92ff9f1c4 100644 --- a/website/content/docs/connect/config-entries/ingress-gateway.mdx +++ b/website/content/docs/connect/config-entries/ingress-gateway.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Ingress Gateway: Configuration Entry Reference +page_title: Ingress Gateway - Configuration Entry Reference description: >- -The ingress gateway configuration entry kind defines behavior to secure incoming communication between the service mesh and external sources. Use the reference guide to learn about `"ingress-gateway"` config entry parameters and exposing TCP and HTTP listeners. + The ingress gateway configuration entry kind defines behavior to secure incoming communication between the service mesh and external sources. Use the reference guide to learn about `""ingress-gateway""` config entry parameters and exposing TCP and HTTP listeners. --- # Ingress Gateway Configuration Entry diff --git a/website/content/docs/connect/config-entries/mesh.mdx b/website/content/docs/connect/config-entries/mesh.mdx index e915e6d8b23d..9cc4c15b28cf 100644 --- a/website/content/docs/connect/config-entries/mesh.mdx +++ b/website/content/docs/connect/config-entries/mesh.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Mesh: Configuration Entry Reference +page_title: Mesh - Configuration Entry Reference description: >- -The mesh configuration entry kind defines global default settings like TLS version requirements for proxies inside the service mesh. Use the reference guide to learn about `""mesh""` config entry parameters and how to control communication with services outside of the mesh. + The mesh configuration entry kind defines global default settings like TLS version requirements for proxies inside the service mesh. Use the reference guide to learn about `""mesh""` config entry parameters and how to control communication with services outside of the mesh. --- # Mesh Configuration Entry diff --git a/website/content/docs/connect/config-entries/proxy-defaults.mdx b/website/content/docs/connect/config-entries/proxy-defaults.mdx index 5f7fe65275b2..ee7de334a579 100644 --- a/website/content/docs/connect/config-entries/proxy-defaults.mdx +++ b/website/content/docs/connect/config-entries/proxy-defaults.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Proxy Defaults: Configuration Entry Reference +page_title: Proxy Defaults - Configuration Entry Reference description: >- -The proxy defaults configuration entry kind defines default behaviors for sidecar proxies in the service mesh. Use the reference guide to learn about `""proxy-defaults""` config entry parameters and how to expose HTTP paths through Envoy. + The proxy defaults configuration entry kind defines default behaviors for sidecar proxies in the service mesh. Use the reference guide to learn about `""proxy-defaults""` config entry parameters and how to expose HTTP paths through Envoy. --- # Proxy Defaults Configuration Entry diff --git a/website/content/docs/connect/config-entries/service-defaults.mdx b/website/content/docs/connect/config-entries/service-defaults.mdx index 80c9c302940b..4bbe9e298a82 100644 --- a/website/content/docs/connect/config-entries/service-defaults.mdx +++ b/website/content/docs/connect/config-entries/service-defaults.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Defaults: Configuration Entry Reference +page_title: Service Defaults - Configuration Entry Reference description: >- -The service defaults configuration entry kind defines sets of default configurations that apply to all services in the mesh. Use the examples learn how to define a default protocol, default upstream configuration, and default terminating gateway. + The service defaults configuration entry kind defines sets of default configurations that apply to all services in the mesh. Use the examples learn how to define a default protocol, default upstream configuration, and default terminating gateway. --- # Service Defaults Configuration Entry diff --git a/website/content/docs/connect/config-entries/service-intentions.mdx b/website/content/docs/connect/config-entries/service-intentions.mdx index aee457889a8b..a7370cc8b284 100644 --- a/website/content/docs/connect/config-entries/service-intentions.mdx +++ b/website/content/docs/connect/config-entries/service-intentions.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Intentions: Configuration Entry Reference +page_title: Service Intentions - Configuration Entry Reference description: >- -The service intentions configuration entry kind defines the communication permissions between service types. Use the reference guide to learn about `""service-intentions""` config entry parameters and how to authorize L4 and L7 communication int he service mesh with intentions. + The service intentions configuration entry kind defines the communication permissions between service types. Use the reference guide to learn about `""service-intentions""` config entry parameters and how to authorize L4 and L7 communication int he service mesh with intentions. --- # Service Intentions Configuration Entry ((#service-intentions)) diff --git a/website/content/docs/connect/config-entries/service-resolver.mdx b/website/content/docs/connect/config-entries/service-resolver.mdx index 0fb6a955516d..f6e52ce010b4 100644 --- a/website/content/docs/connect/config-entries/service-resolver.mdx +++ b/website/content/docs/connect/config-entries/service-resolver.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Resolver: Configuration Entry Reference +page_title: Service Resolver - Configuration Entry Reference description: >- -The service resolver configuration entry kind defines subsets of service instances that satisfy upstream discovery requests. Use the reference guide to learn about `""service-resolver""` config entry parameters and how filtering by service subsets helps route traffic based on properties like version number. + The service resolver configuration entry kind defines subsets of service instances that satisfy upstream discovery requests. Use the reference guide to learn about `""service-resolver""` config entry parameters and how filtering by service subsets helps route traffic based on properties like version number. --- # Service Resolver Configuration Entry diff --git a/website/content/docs/connect/config-entries/service-router.mdx b/website/content/docs/connect/config-entries/service-router.mdx index d14c055b6ec3..e1adaa2023f5 100644 --- a/website/content/docs/connect/config-entries/service-router.mdx +++ b/website/content/docs/connect/config-entries/service-router.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Router: Configuration Entry Reference +page_title: Service Router - Configuration Entry Reference description: >- -The service router configuration entry kind defines where the service mesh routes requests based on L7 network information such as header or path. Use the reference guide to learn about `""service-router""` config entry parameters and how behaviors like request timeouts, retry behavior, header modification, and path rewriting can be applied to a request based on its header or path information. + The service router configuration entry kind defines where the service mesh routes requests based on L7 network information such as header or path. Use the reference guide to learn about `""service-router""` config entry parameters and how behaviors like request timeouts, retry behavior, header modification, and path rewriting can be applied to a request based on its header or path information. --- # Service Router Configuration Entry diff --git a/website/content/docs/connect/config-entries/service-splitter.mdx b/website/content/docs/connect/config-entries/service-splitter.mdx index 40b70fbe9f31..5e37f49c6030 100644 --- a/website/content/docs/connect/config-entries/service-splitter.mdx +++ b/website/content/docs/connect/config-entries/service-splitter.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Splitter: Configuration Entry Reference +page_title: Service Splitter - Configuration Entry Reference description: >- -The service splitter configuration entry kind defines how to divide service mesh traffic between service instances. Use the reference guide to learn about `""service-splitter""` config entry parameters and how it can be used for traffic management behaviors like canary rollouts, blue green deployment, and load balancing across environments. + The service splitter configuration entry kind defines how to divide service mesh traffic between service instances. Use the reference guide to learn about `""service-splitter""` config entry parameters and how it can be used for traffic management behaviors like canary rollouts, blue green deployment, and load balancing across environments. --- # Service Splitter Configuration Entry diff --git a/website/content/docs/connect/config-entries/terminating-gateway.mdx b/website/content/docs/connect/config-entries/terminating-gateway.mdx index ec44dc2fc2ca..d2d2acd1f156 100644 --- a/website/content/docs/connect/config-entries/terminating-gateway.mdx +++ b/website/content/docs/connect/config-entries/terminating-gateway.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Terminating Gateway: Configuration Entry Reference +page_title: Terminating Gateway - Configuration Entry Reference description: >- -The terminating gateway configuration entry kind defines behavior to secure outgoing communication between the service mesh and non-mesh services. Use the reference guide to learn about `""terminating-gateway""` config entry parameters and connecting from your service mesh to external or non-mesh services registered with Consul. + The terminating gateway configuration entry kind defines behavior to secure outgoing communication between the service mesh and non-mesh services. Use the reference guide to learn about `""terminating-gateway""` config entry parameters and connecting from your service mesh to external or non-mesh services registered with Consul. --- # Terminating Gateway Configuration Entry diff --git a/website/content/docs/connect/configuration.mdx b/website/content/docs/connect/configuration.mdx index 9878833ff79e..2bc9216d9844 100644 --- a/website/content/docs/connect/configuration.mdx +++ b/website/content/docs/connect/configuration.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Configuration: Overview +page_title: Service Mesh Configuration - Overview description: >- -Learn how to enable and configure Consul's service mesh capabilities in agent configurations, and how to integrate with schedulers like Kubernetes and Nomad. ""Connect"" is the subsystem that provides Consul’s service mesh capabilities. + Learn how to enable and configure Consul's service mesh capabilities in agent configurations, and how to integrate with schedulers like Kubernetes and Nomad. ""Connect"" is the subsystem that provides Consul’s service mesh capabilities. --- # Service Mesh Configuration Overview diff --git a/website/content/docs/connect/connect-internals.mdx b/website/content/docs/connect/connect-internals.mdx index 19036284c39d..6edc72eace8b 100644 --- a/website/content/docs/connect/connect-internals.mdx +++ b/website/content/docs/connect/connect-internals.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh: How it Works +page_title: Service Mesh - How it Works description: >- -Consul's service mesh enforces secure service communication using mutual TLS (mTLS) encryption and explicit authorization. Learn how the service mesh certificate authorities, intentions, and agents work together in the ""Connect"" subsystem to provide Consul’s service mesh capabilities. + Consul's service mesh enforces secure service communication using mutual TLS (mTLS) encryption and explicit authorization. Learn how the service mesh certificate authorities, intentions, and agents work together in the ""Connect"" subsystem to provide Consul’s service mesh capabilities. --- # How Connect Works diff --git a/website/content/docs/connect/connectivity-tasks.mdx b/website/content/docs/connect/connectivity-tasks.mdx index 45d5ab905073..0b7fd55033fc 100644 --- a/website/content/docs/connect/connectivity-tasks.mdx +++ b/website/content/docs/connect/connectivity-tasks.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Gateway Types description: >- -Ingress, terminating, and mesh gateways are proxies that direct traffic into, out of, and inside of Consul's service mesh. Learn how these gateways enable different kinds of service-to-service communication. + Ingress, terminating, and mesh gateways are proxies that direct traffic into, out of, and inside of Consul's service mesh. Learn how these gateways enable different kinds of service-to-service communication. --- # Types of Gateway Connections in a Service Mesh diff --git a/website/content/docs/connect/dev.mdx b/website/content/docs/connect/dev.mdx index d68aae4fe564..a4d900afa8bb 100644 --- a/website/content/docs/connect/dev.mdx +++ b/website/content/docs/connect/dev.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Service Mesh Debugging description: >- -Use the `consul connect proxy` command to connect to services or masquerade as other services for development and debugging purposes. Example code demonstrates connecting to services that are part of the service mesh as listeners only. + Use the `consul connect proxy` command to connect to services or masquerade as other services for development and debugging purposes. Example code demonstrates connecting to services that are part of the service mesh as listeners only. --- # Service Mesh Debugging diff --git a/website/content/docs/connect/distributed-tracing.mdx b/website/content/docs/connect/distributed-tracing.mdx index 96e61a44d4fb..9c177b82dd9b 100644 --- a/website/content/docs/connect/distributed-tracing.mdx +++ b/website/content/docs/connect/distributed-tracing.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Service Mesh Distributed Tracing description: >- -Distributed tracing tracks the path of a request as it traverses the service mesh. Consul supports distributed tracing for applications that have it implemented. Learn how to integrate tracing libraries in your application and configure Consul to participate in that tracing. + Distributed tracing tracks the path of a request as it traverses the service mesh. Consul supports distributed tracing for applications that have it implemented. Learn how to integrate tracing libraries in your application and configure Consul to participate in that tracing. --- # Distributed Tracing diff --git a/website/content/docs/connect/gateways/index.mdx b/website/content/docs/connect/gateways/index.mdx index cbf8c2e92bcd..15e05583809e 100644 --- a/website/content/docs/connect/gateways/index.mdx +++ b/website/content/docs/connect/gateways/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Gateways Overview description: >- -Gateways are proxies that direct traffic into, out of, and inside of Consul's service mesh. They secure communication with external or non-mesh network resources and enable services on different runtimes, cloud providers, or with overlapping IP addresses to communicate with each other. + Gateways are proxies that direct traffic into, out of, and inside of Consul's service mesh. They secure communication with external or non-mesh network resources and enable services on different runtimes, cloud providers, or with overlapping IP addresses to communicate with each other. --- # Gateways Overview diff --git a/website/content/docs/connect/gateways/ingress-gateway.mdx b/website/content/docs/connect/gateways/ingress-gateway.mdx index e65b9e9210f3..77517d2825c5 100644 --- a/website/content/docs/connect/gateways/ingress-gateway.mdx +++ b/website/content/docs/connect/gateways/ingress-gateway.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Ingress Gateway | Service Mesh description: >- -Ingress gateways listen for requests from external network locations and route authorized traffic to destinations in the service mesh. Use custom TLS certificates with ingress gateways through Envoy's gRPC Secret Discovery Service (SDS). + Ingress gateways listen for requests from external network locations and route authorized traffic to destinations in the service mesh. Use custom TLS certificates with ingress gateways through Envoy's gRPC Secret Discovery Service (SDS). --- # Ingress Gateways diff --git a/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters.mdx b/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters.mdx index 1931df5d93dd..db697488cfd9 100644 --- a/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters.mdx +++ b/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Mesh Gateways between Datacenters description: >- -Mesh gateways are specialized proxies that route data between services that cannot communicate directly. Learn how to enable service-to-service traffic across datacenters and review example configuration entries. + Mesh gateways are specialized proxies that route data between services that cannot communicate directly. Learn how to enable service-to-service traffic across datacenters and review example configuration entries. --- # Mesh Gateways between Datacenters diff --git a/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-partitions.mdx b/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-partitions.mdx index ad3bfe7e1252..dcdf479d6cd3 100644 --- a/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-partitions.mdx +++ b/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-partitions.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Mesh Gateways between Admin Partitions description: >- -Mesh gateways are specialized proxies that route data between services that cannot communicate directly with upstreams. Learn how to enable service-to-service traffic across admin partitions and review example configuration entries. + Mesh gateways are specialized proxies that route data between services that cannot communicate directly with upstreams. Learn how to enable service-to-service traffic across admin partitions and review example configuration entries. --- # Service-to-service Traffic Across Partitions diff --git a/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-peers.mdx b/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-peers.mdx index b8b9b7a7cdee..ad961fbf68cb 100644 --- a/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-peers.mdx +++ b/website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-peers.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Mesh Gateways between Peered Clusters description: >- -Mesh gateways are specialized proxies that route data between services that cannot communicate directly. Learn how to enable service-to-service traffic across clusters in different datacenters or admin partitions that have an established peering connection. + Mesh gateways are specialized proxies that route data between services that cannot communicate directly. Learn how to enable service-to-service traffic across clusters in different datacenters or admin partitions that have an established peering connection. --- # Mesh Gateways between Peered Clusters diff --git a/website/content/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways.mdx b/website/content/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways.mdx index 58c8fec4674a..1de7666e6a8f 100644 --- a/website/content/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways.mdx +++ b/website/content/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Mesh Gateways for WAN Federation description: >- -You can use mesh gateways to simplify the networking requirements for WAN federated Consul datacenters. Mesh gateways reduce cross-datacenter connection paths, ports, and communication protocols. + You can use mesh gateways to simplify the networking requirements for WAN federated Consul datacenters. Mesh gateways reduce cross-datacenter connection paths, ports, and communication protocols. --- # Mesh Gateways for WAN Federation diff --git a/website/content/docs/connect/gateways/terminating-gateway.mdx b/website/content/docs/connect/gateways/terminating-gateway.mdx index 7188e391a30a..0ef906a20ff6 100644 --- a/website/content/docs/connect/gateways/terminating-gateway.mdx +++ b/website/content/docs/connect/gateways/terminating-gateway.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Terminating Gateway | Service Mesh description: >- -Terminating gateways send requests from inside the service mesh to external network locations and services outside the mesh. Learn about requirements and terminating gateway interactions with Consul's service catalog. + Terminating gateways send requests from inside the service mesh to external network locations and services outside the mesh. Learn about requirements and terminating gateway interactions with Consul's service catalog. --- # Terminating Gateways diff --git a/website/content/docs/connect/index.mdx b/website/content/docs/connect/index.mdx index 08b9e92d9d5b..b053aa706b3c 100644 --- a/website/content/docs/connect/index.mdx +++ b/website/content/docs/connect/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Service Mesh on Consul description: >- -Consul’s service mesh makes application and microservice networking secure and observable with identity-based authentication, mutual TLS (mTLS) encryption, and explicit service-to-service authorization enforced by sidecar proxies. Learn how Consul’s service mesh works and get started on VMs or Kubernetes. + Consul’s service mesh makes application and microservice networking secure and observable with identity-based authentication, mutual TLS (mTLS) encryption, and explicit service-to-service authorization enforced by sidecar proxies. Learn how Consul’s service mesh works and get started on VMs or Kubernetes. --- # Consul Service Mesh diff --git a/website/content/docs/connect/intentions-legacy.mdx b/website/content/docs/connect/intentions-legacy.mdx index faf695332735..7d252e8bf168 100644 --- a/website/content/docs/connect/intentions-legacy.mdx +++ b/website/content/docs/connect/intentions-legacy.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Intentions (Legacy Mode) description: >- -Intentions define service communication permissions in the service mesh. As of version 1.9, Consul uses a new system for creating and managing intentions. Learn how intentions worked in earlier versions of Consul with this legacy documentation. + Intentions define service communication permissions in the service mesh. As of version 1.9, Consul uses a new system for creating and managing intentions. Learn how intentions worked in earlier versions of Consul with this legacy documentation. --- # Intentions in Legacy Mode diff --git a/website/content/docs/connect/intentions.mdx b/website/content/docs/connect/intentions.mdx index 38387326487e..bdf83ebb3a90 100644 --- a/website/content/docs/connect/intentions.mdx +++ b/website/content/docs/connect/intentions.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Service Mesh Intentions description: >- -Intentions define communication permissions in the service mesh between microservices. Learn about configuration basics, wildcard intentions, precedence and match order, and protecting intention management with ACLs. + Intentions define communication permissions in the service mesh between microservices. Learn about configuration basics, wildcard intentions, precedence and match order, and protecting intention management with ACLs. --- # Service Mesh Intentions diff --git a/website/content/docs/connect/l7-traffic/discovery-chain.mdx b/website/content/docs/connect/l7-traffic/discovery-chain.mdx index ec49ed52fd97..663927db6758 100644 --- a/website/content/docs/connect/l7-traffic/discovery-chain.mdx +++ b/website/content/docs/connect/l7-traffic/discovery-chain.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Traffic Management: Discovery Chain +page_title: Service Mesh Traffic Management - Discovery Chain description: >- -The discovery chain compiles service router, splitter, and resolver configuration entries to direct traffic to specific instances in a service mesh. Learn about compiled discovery chain results, including discovery graph nodes and targets. + The discovery chain compiles service router, splitter, and resolver configuration entries to direct traffic to specific instances in a service mesh. Learn about compiled discovery chain results, including discovery graph nodes and targets. --- # Discovery Chain for Service Mesh Traffic Management diff --git a/website/content/docs/connect/l7-traffic/index.mdx b/website/content/docs/connect/l7-traffic/index.mdx index ab86b71687b2..2845640ce624 100644 --- a/website/content/docs/connect/l7-traffic/index.mdx +++ b/website/content/docs/connect/l7-traffic/index.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Traffic Management: Overview +page_title: Service Mesh Traffic Management - Overview description: >- -Consul can route, split, and resolve Layer 7 traffic in a service mesh to support workflows like canary testing and blue/green deployments. Learn about the three configuration entry kinds that define L7 traffic management behavior in Consul. + Consul can route, split, and resolve Layer 7 traffic in a service mesh to support workflows like canary testing and blue/green deployments. Learn about the three configuration entry kinds that define L7 traffic management behavior in Consul. --- -> **1.6.0+:** This feature is available in Consul versions 1.6.0 and newer. diff --git a/website/content/docs/connect/native/go.mdx b/website/content/docs/connect/native/go.mdx index c047e95bbbf3..56ee2cd713da 100644 --- a/website/content/docs/connect/native/go.mdx +++ b/website/content/docs/connect/native/go.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Native App Integration: Go Apps +page_title: Service Mesh Native App Integration - Go Apps description: >- -Consul's service mesh supports native integrations of Go applications into the service mesh through a Go library. Example code demonstrates how to connect your Go applications to the service mesh. + Consul's service mesh supports native integrations of Go applications into the service mesh through a Go library. Example code demonstrates how to connect your Go applications to the service mesh. --- # Service Mesh Native Integration for Go Applications diff --git a/website/content/docs/connect/native/index.mdx b/website/content/docs/connect/native/index.mdx index f8d12481f5ce..bae584ca366e 100644 --- a/website/content/docs/connect/native/index.mdx +++ b/website/content/docs/connect/native/index.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Native App Integration: Overview +page_title: Service Mesh Native App Integration - Overview description: >- -When using sidecar proxies is not possible, applications can natively integrate with Consul service mesh, but have reduced access to service mesh features. Learn how “Connect-Native” apps use mTLS to authenticate with Consul and how to add integrations to service registrations. + When using sidecar proxies is not possible, applications can natively integrate with Consul service mesh, but have reduced access to service mesh features. Learn how “Connect-Native” apps use mTLS to authenticate with Consul and how to add integrations to service registrations. --- # Service Mesh Native App Integration Overview diff --git a/website/content/docs/connect/nomad.mdx b/website/content/docs/connect/nomad.mdx index 416fc86a7589..2c013cd3be45 100644 --- a/website/content/docs/connect/nomad.mdx +++ b/website/content/docs/connect/nomad.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Sevice Mesh: Nomad Integration +page_title: Sevice Mesh - Nomad Integration description: >- -Consul's service mesh can be applied to provide secure communication between services managed by Nomad's scheduler and orchestrator functions, including Nomad jobs and task groups. Use the guide and reference documentation to learn more. + Consul's service mesh can be applied to provide secure communication between services managed by Nomad's scheduler and orchestrator functions, including Nomad jobs and task groups. Use the guide and reference documentation to learn more. --- # Consul and Nomad Integration diff --git a/website/content/docs/connect/observability/index.mdx b/website/content/docs/connect/observability/index.mdx index 30f0860763f1..f4ed4f8b9a55 100644 --- a/website/content/docs/connect/observability/index.mdx +++ b/website/content/docs/connect/observability/index.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Observability: Overview +page_title: Service Mesh Observability - Overview description: >- -To use Consul's observability features, configure sidecar proxies in the service mesh to collect and emit L7 metrics. Learn about configuring metrics destinations and a service's protocol and upstreams. + To use Consul's observability features, configure sidecar proxies in the service mesh to collect and emit L7 metrics. Learn about configuring metrics destinations and a service's protocol and upstreams. --- # Service Mesh Observability Overview diff --git a/website/content/docs/connect/observability/ui-visualization.mdx b/website/content/docs/connect/observability/ui-visualization.mdx index ecd152717ad5..33dde103bd5c 100644 --- a/website/content/docs/connect/observability/ui-visualization.mdx +++ b/website/content/docs/connect/observability/ui-visualization.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Observability: UI Visualization +page_title: Service Mesh Observability - UI Visualization description: >- -Consul's UI can display a service's topology and associated metrics from the service mesh. Learn how to configure the UI to collect metrics from your metrics provider, modify access for metrics proxies, and integrate custom metrics providers. + Consul's UI can display a service's topology and associated metrics from the service mesh. Learn how to configure the UI to collect metrics from your metrics provider, modify access for metrics proxies, and integrate custom metrics providers. --- # Service Mesh Observability: UI Visualization diff --git a/website/content/docs/connect/proxies/built-in.mdx b/website/content/docs/connect/proxies/built-in.mdx index ec12d11237e2..c856396b13b0 100644 --- a/website/content/docs/connect/proxies/built-in.mdx +++ b/website/content/docs/connect/proxies/built-in.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Built-in Proxy Configuration | Service Mesh description: >- -Consul includes a built-in L4 proxy with limited capabilities to use for development and testing only. Use the built-in proxy config key reference to learn about the options you can configure. + Consul includes a built-in L4 proxy with limited capabilities to use for development and testing only. Use the built-in proxy config key reference to learn about the options you can configure. --- # Built-in Proxy Configuration for Service Mesh diff --git a/website/content/docs/connect/proxies/envoy.mdx b/website/content/docs/connect/proxies/envoy.mdx index 652e8be9e1ea..014b3e6e5262 100644 --- a/website/content/docs/connect/proxies/envoy.mdx +++ b/website/content/docs/connect/proxies/envoy.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Envoy Proxy Configuration | Service Mesh description: >- -Consul supports Envoy proxies to direct traffic throughout the service mesh. Learn about Consul versions and their Envoy support, and use the reference guide to review options for bootstrap configuration, dynamic configuration, and advanced topics like escape hatch overrides. + Consul supports Envoy proxies to direct traffic throughout the service mesh. Learn about Consul versions and their Envoy support, and use the reference guide to review options for bootstrap configuration, dynamic configuration, and advanced topics like escape hatch overrides. --- # Envoy Proxy Configuration for Service Mesh diff --git a/website/content/docs/connect/proxies/index.mdx b/website/content/docs/connect/proxies/index.mdx index aebab764a28e..bb83041439d5 100644 --- a/website/content/docs/connect/proxies/index.mdx +++ b/website/content/docs/connect/proxies/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Service Mesh Proxy Overview description: >- -In Consul service mesh, each service has a sidecar proxy that secures connections with other services in the mesh without modifying the underlying application code. You can use the built-in proxy, Envoy, or a custom proxy to handle communication and verify TLS connections. + In Consul service mesh, each service has a sidecar proxy that secures connections with other services in the mesh without modifying the underlying application code. You can use the built-in proxy, Envoy, or a custom proxy to handle communication and verify TLS connections. --- # Service Mesh Proxy Overview diff --git a/website/content/docs/connect/proxies/integrate.mdx b/website/content/docs/connect/proxies/integrate.mdx index 92c229957d12..6251cac2ca50 100644 --- a/website/content/docs/connect/proxies/integrate.mdx +++ b/website/content/docs/connect/proxies/integrate.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Custom Proxy Configuration | Service Mesh description: >- -Consul supports custom proxy integrations for service discovery and sidecar instantiation. Learn about proxy requirements for service mesh operations, as well as how to authorize inbound and outbound connections for your custom proxy. + Consul supports custom proxy integrations for service discovery and sidecar instantiation. Learn about proxy requirements for service mesh operations, as well as how to authorize inbound and outbound connections for your custom proxy. --- # Custom Proxy Configuration for Service Mesh diff --git a/website/content/docs/connect/proxies/managed-deprecated.mdx b/website/content/docs/connect/proxies/managed-deprecated.mdx index b714c56791fc..e7b6144a9376 100644 --- a/website/content/docs/connect/proxies/managed-deprecated.mdx +++ b/website/content/docs/connect/proxies/managed-deprecated.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Managed Proxy for Connect (Legacy) description: >- -Consul's service mesh originally included a proxy manager that was deprecated in version 1.6. Learn about the reasons for its deprecation and how it worked with this legacy documentation. + Consul's service mesh originally included a proxy manager that was deprecated in version 1.6. Learn about the reasons for its deprecation and how it worked with this legacy documentation. --- # Managed Proxy for Connect Legacy Documentation diff --git a/website/content/docs/connect/registration/index.mdx b/website/content/docs/connect/registration/index.mdx index dce7510d2006..379174e310c5 100644 --- a/website/content/docs/connect/registration/index.mdx +++ b/website/content/docs/connect/registration/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Service Mesh Proxy Registration Overview description: >- -To make Consul aware of proxies in your service mesh, you must register them. Learn about methods for configuring and registering sidecar proxies. + To make Consul aware of proxies in your service mesh, you must register them. Learn about methods for configuring and registering sidecar proxies. --- # Service Mesh Proxy Overview diff --git a/website/content/docs/connect/registration/service-registration.mdx b/website/content/docs/connect/registration/service-registration.mdx index ca4ad3b44d4f..a27d881c3bfb 100644 --- a/website/content/docs/connect/registration/service-registration.mdx +++ b/website/content/docs/connect/registration/service-registration.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Register a Service Mesh Proxy Outside of a Service Registration description: >- -You can register a service mesh sidecar proxy separately from the registration of the service instance it fronts. Learn about proxy configuration options and how to format them with examples. + You can register a service mesh sidecar proxy separately from the registration of the service instance it fronts. Learn about proxy configuration options and how to format them with examples. --- # Register a Service Mesh Proxy Outside of a Service Registration diff --git a/website/content/docs/connect/registration/sidecar-service.mdx b/website/content/docs/connect/registration/sidecar-service.mdx index b0383dcc251f..8a16a7340433 100644 --- a/website/content/docs/connect/registration/sidecar-service.mdx +++ b/website/content/docs/connect/registration/sidecar-service.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Register a Service Mesh Proxy in a Service Registration description: >- -You can register a service instance and its sidecar proxy at the same time. Learn about default settings, customizable parameters, limitations, and lifecycle behaviors of the sidecar proxy. + You can register a service instance and its sidecar proxy at the same time. Learn about default settings, customizable parameters, limitations, and lifecycle behaviors of the sidecar proxy. --- # Register a Service Mesh Proxy in a Service Registration diff --git a/website/content/docs/connect/security.mdx b/website/content/docs/connect/security.mdx index 9eac374719c5..9975d8f9c163 100644 --- a/website/content/docs/connect/security.mdx +++ b/website/content/docs/connect/security.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh Security: Best Practices +page_title: Service Mesh Security - Best Practices description: >- -Consul provides secure service mesh communication by default. Additional configuration can improve network security by preventing unauthorized access and traffic sniffing. Review security considerations, our recommendations, and best practices. + Consul provides secure service mesh communication by default. Additional configuration can improve network security by preventing unauthorized access and traffic sniffing. Review security considerations, our recommendations, and best practices. --- # Best Practices for Service Mesh Security diff --git a/website/content/docs/connect/transparent-proxy.mdx b/website/content/docs/connect/transparent-proxy.mdx index c6646f52f43a..761a57e134eb 100644 --- a/website/content/docs/connect/transparent-proxy.mdx +++ b/website/content/docs/connect/transparent-proxy.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Service Mesh: Enable Transparent Proxy Mode +page_title: Service Mesh - Enable Transparent Proxy Mode description: >- -Learn how transparent proxy enables Consul on Kubernetes to direct inbound and outbound traffic through the service mesh. Use transparent proxying to increase application security without configuring individual upstream services. + Learn how transparent proxy enables Consul on Kubernetes to direct inbound and outbound traffic through the service mesh. Use transparent proxying to increase application security without configuring individual upstream services. --- # Enable Transparent Proxy Mode diff --git a/website/content/docs/discovery/checks.mdx b/website/content/docs/discovery/checks.mdx index 0926a7e79870..fe34f28fea71 100644 --- a/website/content/docs/discovery/checks.mdx +++ b/website/content/docs/discovery/checks.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Configure Health Checks description: >- -Agents can be configured to periodically perform custom checks on the health of a service instance or node. Learn about the types of health checks and how to define them in agent and service configuration files. + Agents can be configured to periodically perform custom checks on the health of a service instance or node. Learn about the types of health checks and how to define them in agent and service configuration files. --- # Health Checks diff --git a/website/content/docs/discovery/dns.mdx b/website/content/docs/discovery/dns.mdx index 2b6008e3c1e8..4c990b634a5f 100644 --- a/website/content/docs/discovery/dns.mdx +++ b/website/content/docs/discovery/dns.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Find services with DNS description: >- -For service discovery use cases, Domain Name Service (DNS) is the main interface to look up, query, and address Consul nodes and services. Learn how a Consul DNS lookup can help you find services by tag, name, namespace, partition, datacenter, or domain. + For service discovery use cases, Domain Name Service (DNS) is the main interface to look up, query, and address Consul nodes and services. Learn how a Consul DNS lookup can help you find services by tag, name, namespace, partition, datacenter, or domain. --- # Query services with DNS diff --git a/website/content/docs/discovery/services.mdx b/website/content/docs/discovery/services.mdx index 91b209758a3f..5cef8eaf7ee8 100644 --- a/website/content/docs/discovery/services.mdx +++ b/website/content/docs/discovery/services.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Register Services with Service Definitions description: >- -Define and register services and their health checks with Consul to make a service available for service discovery or service mesh access. Learn how to format service definitions with this reference page and sample code. + Define and register services and their health checks with Consul to make a service available for service discovery or service mesh access. Learn how to format service definitions with this reference page and sample code. --- # Register Services with Service Definitions diff --git a/website/content/docs/download-tools.mdx b/website/content/docs/download-tools.mdx index dfbe3e9677eb..7cab9e98f893 100644 --- a/website/content/docs/download-tools.mdx +++ b/website/content/docs/download-tools.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Consul Tools description: >- -Consul's capabilities can be extended through integration with other tools. Learn about Consul-related tools created by HashiCorp and by the Consul community. + Consul's capabilities can be extended through integration with other tools. Learn about Consul-related tools created by HashiCorp and by the Consul community. --- # Download Consul Tools diff --git a/website/content/docs/enterprise/admin-partitions.mdx b/website/content/docs/enterprise/admin-partitions.mdx index 8b90cfaa7b0d..e3712f0314ff 100644 --- a/website/content/docs/enterprise/admin-partitions.mdx +++ b/website/content/docs/enterprise/admin-partitions.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Admin Partitions (Enterprise) description: >- -Admin partitions define boundaries between services managed by separate teams, enabling a service mesh across k8s clusters controlled by a single Consul server. Learn about their requirements and how to deploy admin partitions on Kubernetes. + Admin partitions define boundaries between services managed by separate teams, enabling a service mesh across k8s clusters controlled by a single Consul server. Learn about their requirements and how to deploy admin partitions on Kubernetes. --- # Consul Enterprise Admin Partitions diff --git a/website/content/docs/enterprise/audit-logging.mdx b/website/content/docs/enterprise/audit-logging.mdx index c7fd4e12c21b..4a2b85b71391 100644 --- a/website/content/docs/enterprise/audit-logging.mdx +++ b/website/content/docs/enterprise/audit-logging.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Audit Logging (Enterprise) description: >- -Audit logging secures Consul by capturing a record of HTTP API access and usage. Learn how to format agent configuration files to enable audit logs and specify the path to save logs to. + Audit logging secures Consul by capturing a record of HTTP API access and usage. Learn how to format agent configuration files to enable audit logs and specify the path to save logs to. --- # Audit Logging diff --git a/website/content/docs/enterprise/backups.mdx b/website/content/docs/enterprise/backups.mdx index e03171c45ea0..1c776d9856a7 100644 --- a/website/content/docs/enterprise/backups.mdx +++ b/website/content/docs/enterprise/backups.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Automated Backups (Enterprise) description: >- -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. + 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 diff --git a/website/content/docs/enterprise/federation.mdx b/website/content/docs/enterprise/federation.mdx index 09098e2213fb..1e91dfd96ad9 100644 --- a/website/content/docs/enterprise/federation.mdx +++ b/website/content/docs/enterprise/federation.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Federated Network Areas (Enterprise) description: >- -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. + 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 diff --git a/website/content/docs/enterprise/index.mdx b/website/content/docs/enterprise/index.mdx index 786b83dba7a7..5dc06dc06016 100644 --- a/website/content/docs/enterprise/index.mdx +++ b/website/content/docs/enterprise/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Consul Enterprise description: >- -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 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 diff --git a/website/content/docs/enterprise/license/faq.mdx b/website/content/docs/enterprise/license/faq.mdx index c955febf4075..17e5809fa671 100644 --- a/website/content/docs/enterprise/license/faq.mdx +++ b/website/content/docs/enterprise/license/faq.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Enterprise License FAQ description: >- -Review frequently asked questions (FAQs) about Consul Enterprise licenses to learn more about how licenses work, what happens when they expire, and how to get a trial license. + Review frequently asked questions (FAQs) about Consul Enterprise licenses to learn more about how licenses work, what happens when they expire, and how to get a trial license. --- # Frequently Asked Questions (FAQ) diff --git a/website/content/docs/enterprise/license/overview.mdx b/website/content/docs/enterprise/license/overview.mdx index 6e19d4abd98a..68e64aa7e636 100644 --- a/website/content/docs/enterprise/license/overview.mdx +++ b/website/content/docs/enterprise/license/overview.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Enterprise Licenses description: >- -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 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 diff --git a/website/content/docs/enterprise/namespaces.mdx b/website/content/docs/enterprise/namespaces.mdx index 226c34b05179..31e93f42a21f 100644 --- a/website/content/docs/enterprise/namespaces.mdx +++ b/website/content/docs/enterprise/namespaces.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Namespaces (Enterprise) description: >- -Namespaces reduce operational challenges in large deployments. Learn how to define a namespace so that multiple users or teams can access and use the same datacenter without impacting each other. + Namespaces reduce operational challenges in large deployments. Learn how to define a namespace so that multiple users or teams can access and use the same datacenter without impacting each other. --- # Consul Enterprise Namespaces diff --git a/website/content/docs/enterprise/network-segments.mdx b/website/content/docs/enterprise/network-segments.mdx index 49ecb65ec975..d554cdda2c9e 100644 --- a/website/content/docs/enterprise/network-segments.mdx +++ b/website/content/docs/enterprise/network-segments.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Network Segments (Enterprise) description: >- -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 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 diff --git a/website/content/docs/enterprise/read-scale.mdx b/website/content/docs/enterprise/read-scale.mdx index 24f0989a4198..7eede31449b6 100644 --- a/website/content/docs/enterprise/read-scale.mdx +++ b/website/content/docs/enterprise/read-scale.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Read Replicas (Enterprise) description: >- -Learn how you can add non-voting servers to datacenters 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 diff --git a/website/content/docs/enterprise/redundancy.mdx b/website/content/docs/enterprise/redundancy.mdx index 16efa3f0bba8..627a98c77890 100644 --- a/website/content/docs/enterprise/redundancy.mdx +++ b/website/content/docs/enterprise/redundancy.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Redundancy Zones (Enterprise) description: >- -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 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 diff --git a/website/content/docs/enterprise/sentinel.mdx b/website/content/docs/enterprise/sentinel.mdx index 6a61c1507ec6..26e4796d95d4 100644 --- a/website/content/docs/enterprise/sentinel.mdx +++ b/website/content/docs/enterprise/sentinel.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Sentinel in Consul (Enterprise) description: >- -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 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 diff --git a/website/content/docs/enterprise/upgrades.mdx b/website/content/docs/enterprise/upgrades.mdx index c479da29a1fc..b27b1f987e0c 100644 --- a/website/content/docs/enterprise/upgrades.mdx +++ b/website/content/docs/enterprise/upgrades.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Automated Upgrades (Enterprise) description: >- -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 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 diff --git a/website/content/docs/install/bootstrapping.mdx b/website/content/docs/install/bootstrapping.mdx index e88f528108a2..b86783a305ad 100644 --- a/website/content/docs/install/bootstrapping.mdx +++ b/website/content/docs/install/bootstrapping.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Bootstrap a Datacenter 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 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. --- # Bootstrap a Datacenter diff --git a/website/content/docs/install/cloud-auto-join.mdx b/website/content/docs/install/cloud-auto-join.mdx index 40db8699a33a..3e15eb2f86d7 100644 --- a/website/content/docs/install/cloud-auto-join.mdx +++ b/website/content/docs/install/cloud-auto-join.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Auto-join a Cloud Provider description: >- -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. + 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 diff --git a/website/content/docs/install/glossary.mdx b/website/content/docs/install/glossary.mdx index 56b444eefa0e..bdcba9b95c62 100644 --- a/website/content/docs/install/glossary.mdx +++ b/website/content/docs/install/glossary.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Glossary description: >- -The glossary is a list of technical terms with a specific meaning in Consul. Use the glossary to understand Consul concepts and study for the certification exam. + The glossary is a list of technical terms with a specific meaning in Consul. Use the glossary to understand Consul concepts and study for the certification exam. --- # Consul Vocabulary diff --git a/website/content/docs/install/index.mdx b/website/content/docs/install/index.mdx index 55578c2695de..bb7bb6783b25 100644 --- a/website/content/docs/install/index.mdx +++ b/website/content/docs/install/index.mdx @@ -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 source. + 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 diff --git a/website/content/docs/install/manual-bootstrap.mdx b/website/content/docs/install/manual-bootstrap.mdx index 9511d78994b4..5d03e77f79b2 100644 --- a/website/content/docs/install/manual-bootstrap.mdx +++ b/website/content/docs/install/manual-bootstrap.mdx @@ -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. For Consul v0.4+, we recommend automatic bootstrapping 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 diff --git a/website/content/docs/install/performance.mdx b/website/content/docs/install/performance.mdx index aceee5e31659..79f5c597bc2b 100644 --- a/website/content/docs/install/performance.mdx +++ b/website/content/docs/install/performance.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Server Performance Requirements description: >- -Consul servers require sufficient compute 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 diff --git a/website/content/docs/install/ports.mdx b/website/content/docs/install/ports.mdx index e5575cdc28c6..58f067209c96 100644 --- a/website/content/docs/install/ports.mdx +++ b/website/content/docs/install/ports.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Required Ports description: >- -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. + 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 diff --git a/website/content/docs/integrate/nia-integration.mdx b/website/content/docs/integrate/nia-integration.mdx index 52f630985619..29cde3663bfd 100644 --- a/website/content/docs/integrate/nia-integration.mdx +++ b/website/content/docs/integrate/nia-integration.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Network Infrastructure Automation (NIA) Integration Program description: >- -The Network Infrastructure Automation (NIA) Integration Program allows partners to develop Terraform modules for Consul-Terraform-Sync (CTS) that HashiCorp reviews to consider publishing as officially verified. Learn about how to participate in the program. + The Network Infrastructure Automation (NIA) Integration Program allows partners to develop Terraform modules for Consul-Terraform-Sync (CTS) that HashiCorp reviews to consider publishing as officially verified. Learn about how to participate in the program. --- # Network Infrastructure Automation Integration Program diff --git a/website/content/docs/integrate/partnerships.mdx b/website/content/docs/integrate/partnerships.mdx index fb2b6c08fd52..f6818e408a9b 100644 --- a/website/content/docs/integrate/partnerships.mdx +++ b/website/content/docs/integrate/partnerships.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Consul Integration Program description: >- -The Consul Integration Program allows approved partners to develop Consul integrations that HashiCorp reviews to consider publishing as officially verified. Learn about how to participate in the program. + The Consul Integration Program allows approved partners to develop Consul integrations that HashiCorp reviews to consider publishing as officially verified. Learn about how to participate in the program. --- # Consul Integration Program diff --git a/website/content/docs/internals/index.mdx b/website/content/docs/internals/index.mdx index d34baedab6de..ae82e5e0350c 100644 --- a/website/content/docs/internals/index.mdx +++ b/website/content/docs/internals/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Internals Overview description: >- -To enhance your understanding of how to use, troubleshoot, and secure Consul, learn more about Consul's internal properties and how it works under the hood. + To enhance your understanding of how to use, troubleshoot, and secure Consul, learn more about Consul's internal properties and how it works under the hood. --- # Consul Internals Overview diff --git a/website/content/docs/intro/usecases/what-is-a-service-mesh.mdx b/website/content/docs/intro/usecases/what-is-a-service-mesh.mdx index 67a1b129c220..4d4ba30f36e8 100644 --- a/website/content/docs/intro/usecases/what-is-a-service-mesh.mdx +++ b/website/content/docs/intro/usecases/what-is-a-service-mesh.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Service Mesh Explained description: >- -Service mesh is a dedicated network layer for secure, resilient, observable microservice communication. Learn about using Consul's service mesh to solve service networking challenges in application architectures and manage complexity in multi-cloud, hybrid cloud, and multi-platform environments. + Service mesh is a dedicated network layer for secure, resilient, observable microservice communication. Learn about using Consul's service mesh to solve service networking challenges in application architectures and manage complexity in multi-cloud, hybrid cloud, and multi-platform environments. --- # What is a service mesh? diff --git a/website/content/docs/intro/usecases/what-is-service-discovery.mdx b/website/content/docs/intro/usecases/what-is-service-discovery.mdx index a0ce572f79dd..6fb2fabaa544 100644 --- a/website/content/docs/intro/usecases/what-is-service-discovery.mdx +++ b/website/content/docs/intro/usecases/what-is-service-discovery.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Service Discovery Explained description: >- -Service discovery dynamically tracks and monitors service instances on your network and makes them discoverable through DNS queries. Learn about the benefits of service discovery and how it works. + Service discovery dynamically tracks and monitors service instances on your network and makes them discoverable through DNS queries. Learn about the benefits of service discovery and how it works. --- # What is service discovery? diff --git a/website/content/docs/k8s/annotations-and-labels.mdx b/website/content/docs/k8s/annotations-and-labels.mdx index 5420befd99ee..700e1e8bcc5c 100644 --- a/website/content/docs/k8s/annotations-and-labels.mdx +++ b/website/content/docs/k8s/annotations-and-labels.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Annotations and Labels description: >- -Annotations and labels configure Consul sidecar properties and injection behavior when scheduling Kubernetes clusters. Learn about the annotations and labels that enable Consul’s service mesh and secure upstream communication on k8s in this reference guide. + Annotations and labels configure Consul sidecar properties and injection behavior when scheduling Kubernetes clusters. Learn about the annotations and labels that enable Consul’s service mesh and secure upstream communication on k8s in this reference guide. --- # Annotations and Labels diff --git a/website/content/docs/k8s/architecture.mdx b/website/content/docs/k8s/architecture.mdx index e507dad2c5f7..25b9153f3352 100644 --- a/website/content/docs/k8s/architecture.mdx +++ b/website/content/docs/k8s/architecture.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Consul on Kubernetes Control Plane Architecture description: >- -When running on Kubernetes, Consul’s control plane architecture does not change significantly. Server agents are deployed as a StatefulSet with a persistent volume, while client agents run as a k8s DaemonSet with an exposed API port. + When running on Kubernetes, Consul’s control plane architecture does not change significantly. Server agents are deployed as a StatefulSet with a persistent volume, while client agents run as a k8s DaemonSet with an exposed API port. --- diff --git a/website/content/docs/k8s/compatibility.mdx b/website/content/docs/k8s/compatibility.mdx index ce9272af6759..cba5b3e655b3 100644 --- a/website/content/docs/k8s/compatibility.mdx +++ b/website/content/docs/k8s/compatibility.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Consul on Kubernetes Version Compatibility description: >- -New releases require corresponding version updates to Consul on Kubernetes and its Helm chart. Review the compatibility matrix for Consul and consul-k8s and additional notes for integrating Vault and third-party platforms. + New releases require corresponding version updates to Consul on Kubernetes and its Helm chart. Review the compatibility matrix for Consul and consul-k8s and additional notes for integrating Vault and third-party platforms. --- # Consul on Kubernetes Version Compatibility diff --git a/website/content/docs/k8s/connect/connect-ca-provider.mdx b/website/content/docs/k8s/connect/connect-ca-provider.mdx index 663c49a23686..d13407be3881 100644 --- a/website/content/docs/k8s/connect/connect-ca-provider.mdx +++ b/website/content/docs/k8s/connect/connect-ca-provider.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Configure Certificate Authority (CA) for Consul on Kubernetes description: >- -Consul includes a built-in CA, but when bootstrapping a cluster on k8s, you can configure your service mesh to use a custom certificate provider instead. Learn how to configure Vault as an external CA in primary and secondary datacenters and manually rotate Vault tokens. + Consul includes a built-in CA, but when bootstrapping a cluster on k8s, you can configure your service mesh to use a custom certificate provider instead. Learn how to configure Vault as an external CA in primary and secondary datacenters and manually rotate Vault tokens. ---" # Configure Certificate Authority (CA) for Consul on Kubernetes diff --git a/website/content/docs/k8s/connect/health.mdx b/website/content/docs/k8s/connect/health.mdx index 1b78c3e83b46..7f84608c548c 100644 --- a/website/content/docs/k8s/connect/health.mdx +++ b/website/content/docs/k8s/connect/health.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Configure Health Checks for Consul on Kubernetes description: >- -Kubernetes has built-in health probes you can sync with Consul's health checks to ensure service mesh traffic is routed to healthy pods. Learn how to register a TTL Health check and use mutating webhooks to redirect k8s liveness, readiness, and startup probes through Envoy proxies. + Kubernetes has built-in health probes you can sync with Consul's health checks to ensure service mesh traffic is routed to healthy pods. Learn how to register a TTL Health check and use mutating webhooks to redirect k8s liveness, readiness, and startup probes through Envoy proxies. --- # Configure Health Checks for Consul on Kubernetes diff --git a/website/content/docs/k8s/connect/index.mdx b/website/content/docs/k8s/connect/index.mdx index 7e1bce17f072..790f39ca94f3 100644 --- a/website/content/docs/k8s/connect/index.mdx +++ b/website/content/docs/k8s/connect/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: How does Consul Service Mesh Work on Kubernetes? description: >- -An injection annotation allows Consul to automatically deploy sidecar proxies on Kubernetes pods, enabling Consul's service mesh for containers running on k8s. Learn how to configure sidecars, enable services with multiple ports, change default injection settings. + An injection annotation allows Consul to automatically deploy sidecar proxies on Kubernetes pods, enabling Consul's service mesh for containers running on k8s. Learn how to configure sidecars, enable services with multiple ports, change default injection settings. --- # Consul Service Mesh on Kubernetes diff --git a/website/content/docs/k8s/connect/ingress-controllers.mdx b/website/content/docs/k8s/connect/ingress-controllers.mdx index 10ba41b22c54..b630cde8aca4 100644 --- a/website/content/docs/k8s/connect/ingress-controllers.mdx +++ b/website/content/docs/k8s/connect/ingress-controllers.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Configure Ingress Controllers for Consul on Kubernetes description: >- -Ingress controllers are pluggable components that must be configured in k8s in order to use the Ingress resource. Learn how to deploy sidecars with the controller to secure its communication with Consul, review common configuration issues, and find links to example configurations. + Ingress controllers are pluggable components that must be configured in k8s in order to use the Ingress resource. Learn how to deploy sidecars with the controller to secure its communication with Consul, review common configuration issues, and find links to example configurations. --- # Configure Ingress Controllers for Consul on Kubernetes diff --git a/website/content/docs/k8s/connect/ingress-gateways.mdx b/website/content/docs/k8s/connect/ingress-gateways.mdx index de454d698147..bca9b6735daf 100644 --- a/website/content/docs/k8s/connect/ingress-gateways.mdx +++ b/website/content/docs/k8s/connect/ingress-gateways.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Configure Ingress Gateways for Consul on Kubernetes description: >- -Ingress gateways listen for external requests and route authorized traffic to instances in the service mesh running on Kubernetes. Learn how to configure ingress gateways, set intentions, and connect them to k8s applications. + Ingress gateways listen for external requests and route authorized traffic to instances in the service mesh running on Kubernetes. Learn how to configure ingress gateways, set intentions, and connect them to k8s applications. --- # Configure Ingress Gateways for Consul on Kubernetes diff --git a/website/content/docs/k8s/connect/observability/metrics.mdx b/website/content/docs/k8s/connect/observability/metrics.mdx index 40d2f68a1e10..05a562ca484d 100644 --- a/website/content/docs/k8s/connect/observability/metrics.mdx +++ b/website/content/docs/k8s/connect/observability/metrics.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Configure metrics for Consul on Kubernetes description: >- -Use the `connectInject.metrics` Helm values to enable Prometheus and Grafana integrations and capture metrics. Consul can collect metrics from the service mesh, sidecar proxies, agents, and gateways in a k8s cluster and then display service traffic metrics in Consul’s UI for additional observability. + Use the `connectInject.metrics` Helm values to enable Prometheus and Grafana integrations and capture metrics. Consul can collect metrics from the service mesh, sidecar proxies, agents, and gateways in a k8s cluster and then display service traffic metrics in Consul’s UI for additional observability. --- # Configure Metrics for Consul on Kubernetes diff --git a/website/content/docs/k8s/connect/terminating-gateways.mdx b/website/content/docs/k8s/connect/terminating-gateways.mdx index cf1641a1d7a3..309caad20a3f 100644 --- a/website/content/docs/k8s/connect/terminating-gateways.mdx +++ b/website/content/docs/k8s/connect/terminating-gateways.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Configure Terminating Gateways for Consul on Kubernetes description: >- -Terminating gateways send secure requests from the service mesh to locations outside of the Kubernetes cluster. Learn how to configure terminating gateways for k8s, register external services in Consul’s service catalog, and define external sources as upstreams in your service mesh. + Terminating gateways send secure requests from the service mesh to locations outside of the Kubernetes cluster. Learn how to configure terminating gateways for k8s, register external services in Consul’s service catalog, and define external sources as upstreams in your service mesh. --- # Configure Terminating Gateways for Consul on Kubernetes diff --git a/website/content/docs/k8s/crds/index.mdx b/website/content/docs/k8s/crds/index.mdx index b8598407fef2..4e15ef36d1c4 100644 --- a/website/content/docs/k8s/crds/index.mdx +++ b/website/content/docs/k8s/crds/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Custom Resource Definitions for Consul on Kubernetes description: >- -Consul on Kubernetes supports Consul's configuration entry kind through Custom Resource Definitions (CRDs). Learn how to configure Helm charts to enable CRDs and use kubectl to create, manage, and delete mesh components like gateways and intentions on k8s. + Consul on Kubernetes supports Consul's configuration entry kind through Custom Resource Definitions (CRDs). Learn how to configure Helm charts to enable CRDs and use kubectl to create, manage, and delete mesh components like gateways and intentions on k8s. --- # Custom Resource Definitions (CRDs) for Consul on Kubernetes diff --git a/website/content/docs/k8s/crds/upgrade-to-crds.mdx b/website/content/docs/k8s/crds/upgrade-to-crds.mdx index 4dc5ab7325ab..f8a393bd250e 100644 --- a/website/content/docs/k8s/crds/upgrade-to-crds.mdx +++ b/website/content/docs/k8s/crds/upgrade-to-crds.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Upgrade Existing Clusters to Use Custom Resource Definitions description: >- -Kubernetes clusters configured with a Consul Helm chart version older than 0.30.0 require updates in order to use CRDs. Learn about upgrading to a supported Helm version and how to migrate a Consul config entry to a k8s CRD. + Kubernetes clusters configured with a Consul Helm chart version older than 0.30.0 require updates in order to use CRDs. Learn about upgrading to a supported Helm version and how to migrate a Consul config entry to a k8s CRD. --- # Upgrade Existing Clusters to Use Custom Resource Definitions diff --git a/website/content/docs/k8s/dns.mdx b/website/content/docs/k8s/dns.mdx index 6db0f664e86c..c5c89c8347b6 100644 --- a/website/content/docs/k8s/dns.mdx +++ b/website/content/docs/k8s/dns.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Resolve Consul DNS requests in Kubernetes description: >- -Use a k8s ConfigMap to configure KubeDNS or CoreDNS so that you can use Consul's `.service.consul` syntax for queries and other DNS requests. In Kubernetes, this process uses either stub-domain or proxy configuration. + Use a k8s ConfigMap to configure KubeDNS or CoreDNS so that you can use Consul's `.service.consul` syntax for queries and other DNS requests. In Kubernetes, this process uses either stub-domain or proxy configuration. --- # Resolve Consul DNS Requests in Kubernetes diff --git a/website/content/docs/k8s/helm.mdx b/website/content/docs/k8s/helm.mdx index c1f7cf5af30f..9f6bfccb922e 100644 --- a/website/content/docs/k8s/helm.mdx +++ b/website/content/docs/k8s/helm.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Helm Chart Reference description: >- -The Helm Chart allows you to schedule Kubernetes clusters with injected Consul sidecars by defining custom values in a YAML configuration. Find stanza hierarchy, the parameters you can set, and their default values in this k8s reference guide. + The Helm Chart allows you to schedule Kubernetes clusters with injected Consul sidecars by defining custom values in a YAML configuration. Find stanza hierarchy, the parameters you can set, and their default values in this k8s reference guide. --- # Helm Chart Reference diff --git a/website/content/docs/k8s/index.mdx b/website/content/docs/k8s/index.mdx index 2dbb9ba04524..7a425bac2489 100644 --- a/website/content/docs/k8s/index.mdx +++ b/website/content/docs/k8s/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Consul on Kubernetes description: >- -Consul supports Kubernetes natively, allowing you to deploy Consul sidecars to a Kubernetes service mesh and sync the k8s service registry with non-k8s services. Learn how to install Consul on Kubernetes with Helm or the Consul K8s CLI and get started with tutorials. + Consul supports Kubernetes natively, allowing you to deploy Consul sidecars to a Kubernetes service mesh and sync the k8s service registry with non-k8s services. Learn how to install Consul on Kubernetes with Helm or the Consul K8s CLI and get started with tutorials. --- # Consul on Kubernetes diff --git a/website/content/docs/k8s/installation/install-cli.mdx b/website/content/docs/k8s/installation/install-cli.mdx index 88d2f90962ee..15de81117cfc 100644 --- a/website/content/docs/k8s/installation/install-cli.mdx +++ b/website/content/docs/k8s/installation/install-cli.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Install Consul on K8s CLI description: >- -You can use the Consul K8s CLI tool to schedule Kubernetes deployments instead of using Helm. Learn how to download and install the tool to interact with Consul on Kubernetes using the `consul-k8s` command. + You can use the Consul K8s CLI tool to schedule Kubernetes deployments instead of using Helm. Learn how to download and install the tool to interact with Consul on Kubernetes using the `consul-k8s` command. --- # Install Consul on K8s CLI diff --git a/website/content/docs/k8s/installation/install.mdx b/website/content/docs/k8s/installation/install.mdx index 34d13371e3ea..40f743c44eb1 100644 --- a/website/content/docs/k8s/installation/install.mdx +++ b/website/content/docs/k8s/installation/install.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Install Consul on Kubernetes with Helm description: >- -You can use Helm to configure Consul on Kubernetes deployments. Learn how to add the official Helm chart to your repository and the parameters that enable the service mesh, CNI plugins, Consul UI, and Consul HTTP API. + You can use Helm to configure Consul on Kubernetes deployments. Learn how to add the official Helm chart to your repository and the parameters that enable the service mesh, CNI plugins, Consul UI, and Consul HTTP API. --- # Install Consul on Kubernetes with Helm diff --git a/website/content/docs/k8s/installation/platforms/self-hosted-kubernetes.mdx b/website/content/docs/k8s/installation/platforms/self-hosted-kubernetes.mdx index 60e7ce994cbe..42bef6a43a05 100644 --- a/website/content/docs/k8s/installation/platforms/self-hosted-kubernetes.mdx +++ b/website/content/docs/k8s/installation/platforms/self-hosted-kubernetes.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Install Consul on Self-Hosted Kubernetes Clusters description: >- -The process for installing Consul on Kubernetes is the same as installing it on cloud-hosted k8s platforms, but requires additional configuration. Learn how to pre-define Persistent Volume Claims (PVCs) and a default storage class for server agents. + The process for installing Consul on Kubernetes is the same as installing it on cloud-hosted k8s platforms, but requires additional configuration. Learn how to pre-define Persistent Volume Claims (PVCs) and a default storage class for server agents. --- # Install Consul on Self-Hosted Kubernetes Clusters diff --git a/website/content/docs/k8s/k8s-cli.mdx b/website/content/docs/k8s/k8s-cli.mdx index 1a59e5dbffd7..3bc15267ccbe 100644 --- a/website/content/docs/k8s/k8s-cli.mdx +++ b/website/content/docs/k8s/k8s-cli.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Consul on Kubernetes CLI Reference description: >- -The Consul on Kubernetes CLI tool enables you to manage Consul with the `consul-k8s` command instead of direct interaction with Helm, kubectl, or Consul’s CLI. Learn about commands, their flags, and review examples in this reference guide. + The Consul on Kubernetes CLI tool enables you to manage Consul with the `consul-k8s` command instead of direct interaction with Helm, kubectl, or Consul’s CLI. Learn about commands, their flags, and review examples in this reference guide. --- # Consul K8s CLI Reference diff --git a/website/content/docs/k8s/operations/certificate-rotation.mdx b/website/content/docs/k8s/operations/certificate-rotation.mdx index a7337abb65e9..939771054a79 100644 --- a/website/content/docs/k8s/operations/certificate-rotation.mdx +++ b/website/content/docs/k8s/operations/certificate-rotation.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Rotate TLS Certificates for Consul on Kubernetes description: >- -In Consul Helm version 0.29.0 and later, new server agent TLS certificates are issued every time the Helm version is upgraded. Learn how to manually trigger certificate rotation if they do not rotate automatically. + In Consul Helm version 0.29.0 and later, new server agent TLS certificates are issued every time the Helm version is upgraded. Learn how to manually trigger certificate rotation if they do not rotate automatically. --- # Rotate TLS Certificates for Consul on Kubernetes diff --git a/website/content/docs/k8s/operations/gossip-encryption-key-rotation.mdx b/website/content/docs/k8s/operations/gossip-encryption-key-rotation.mdx index 4af30c5314d1..373196e30e8d 100644 --- a/website/content/docs/k8s/operations/gossip-encryption-key-rotation.mdx +++ b/website/content/docs/k8s/operations/gossip-encryption-key-rotation.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Rotate Gossip Encryption Keys for Consul on Kubernetes description: >- -Consul agents use encryption keys to secure their gossip communication, and you must rotate the keys periodically to maintain network security. Learn how to use `keygen` and `keyring` commands to rotate keys for agents on k8s clusters. + Consul agents use encryption keys to secure their gossip communication, and you must rotate the keys periodically to maintain network security. Learn how to use `keygen` and `keyring` commands to rotate keys for agents on k8s clusters. --- # Rotate Gossip Encryption Keys for Consul on Kubernetes diff --git a/website/content/docs/k8s/operations/tls-on-existing-cluster.mdx b/website/content/docs/k8s/operations/tls-on-existing-cluster.mdx index 07ffa89ddc67..ad43186c0361 100644 --- a/website/content/docs/k8s/operations/tls-on-existing-cluster.mdx +++ b/website/content/docs/k8s/operations/tls-on-existing-cluster.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Rolling Updates to TLS for Existing Clusters on Kubernetes description: >- -Consul Helm chart 0.16.0 and later supports TLS communication within clusters. Follow the instructions to trigger rolling updates for consul-k8s without causing downtime. + Consul Helm chart 0.16.0 and later supports TLS communication within clusters. Follow the instructions to trigger rolling updates for consul-k8s without causing downtime. --- # Rolling Updates to TLS for Existing Clusters on Kubernetes diff --git a/website/content/docs/k8s/operations/uninstall.mdx b/website/content/docs/k8s/operations/uninstall.mdx index bdcacca8554d..86a8074dc31e 100644 --- a/website/content/docs/k8s/operations/uninstall.mdx +++ b/website/content/docs/k8s/operations/uninstall.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Uninstall Consul on Kubernetes description: >- -You can use the Consul-K8s CLI tool to remove all or part of a Consul installation on Kubernetes. You can also use Helm and then manually remove resources that Helm does not delete. + You can use the Consul-K8s CLI tool to remove all or part of a Consul installation on Kubernetes. You can also use Helm and then manually remove resources that Helm does not delete. --- # Uninstall Consul on Kubernetes diff --git a/website/content/docs/k8s/service-sync.mdx b/website/content/docs/k8s/service-sync.mdx index 9effcd05eaf8..577aaccff88f 100644 --- a/website/content/docs/k8s/service-sync.mdx +++ b/website/content/docs/k8s/service-sync.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Service Sync for Consul on Kubernetes description: >- -Service sync is a Consul on Kubernetes feature that makes Kubernetes and Consul services available to each other. Learn how to configure Helm values so services can communicate and make Kubernetes services appear in the Consul UI. + Service sync is a Consul on Kubernetes feature that makes Kubernetes and Consul services available to each other. Learn how to configure Helm values so services can communicate and make Kubernetes services appear in the Consul UI. --- # Service Sync for Consul on Kubernetes diff --git a/website/content/docs/k8s/upgrade/index.mdx b/website/content/docs/k8s/upgrade/index.mdx index 42ca17eff6f7..b8471cebe6b4 100644 --- a/website/content/docs/k8s/upgrade/index.mdx +++ b/website/content/docs/k8s/upgrade/index.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Upgrading Consul on Kubernetes Components description: >- -Consul on Kubernetes relies on packages and binaries that have individual upgrade requirements. Learn how to update Helm configurations, Helm versions, Consul versions, and Consul agents, as well as how to determine what will change and its impact on your service mesh. + Consul on Kubernetes relies on packages and binaries that have individual upgrade requirements. Learn how to update Helm configurations, Helm versions, Consul versions, and Consul agents, as well as how to determine what will change and its impact on your service mesh. --- # Upgrading Consul on Kubernetes Components diff --git a/website/content/docs/k8s/upgrade/upgrade-cli.mdx b/website/content/docs/k8s/upgrade/upgrade-cli.mdx index ae835a461363..692d497d56f5 100644 --- a/website/content/docs/k8s/upgrade/upgrade-cli.mdx +++ b/website/content/docs/k8s/upgrade/upgrade-cli.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Update the Consul K8s CLI description: >- -The Consul on Kubernetes CLI tool helps you schedule clusters without direct interaction with Helm or Consul’s CLI. Learn how to update the consul-k8s CLI tool to a new version. + The Consul on Kubernetes CLI tool helps you schedule clusters without direct interaction with Helm or Consul’s CLI. Learn how to update the consul-k8s CLI tool to a new version. --- # Update the Consul K8s CLI diff --git a/website/content/docs/security/acl/acl-federated-datacenters.mdx b/website/content/docs/security/acl/acl-federated-datacenters.mdx index 65c7ec8b6cb5..3909fbe6c2ae 100644 --- a/website/content/docs/security/acl/acl-federated-datacenters.mdx +++ b/website/content/docs/security/acl/acl-federated-datacenters.mdx @@ -2,7 +2,7 @@ layout: docs page_title: ACL Setup for WAN Federated Datacenters description: >- -Consul's access control list (ACL) system can span multiple datacenters that are WAN federated. Learn how to replicate the ACL system from the primary datacenter to secondary datacenters using a replication token. + Consul's access control list (ACL) system can span multiple datacenters that are WAN federated. Learn how to replicate the ACL system from the primary datacenter to secondary datacenters using a replication token. --- # ACLs in Federated Datacenters diff --git a/website/content/docs/security/acl/acl-legacy.mdx b/website/content/docs/security/acl/acl-legacy.mdx index ec3213e206ea..695c2359bf99 100644 --- a/website/content/docs/security/acl/acl-legacy.mdx +++ b/website/content/docs/security/acl/acl-legacy.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Legacy ACL System description: >- -Consul's legacy ACL system was deprecated in version 1.4.0 and removed in version 1.11.0. Learn how Consul's legacy ACL system worked and how it differs from the current ACL system. + Consul's legacy ACL system was deprecated in version 1.4.0 and removed in version 1.11.0. Learn how Consul's legacy ACL system worked and how it differs from the current ACL system. --- # ACL System in Legacy Mode diff --git a/website/content/docs/security/acl/acl-migrate-tokens.mdx b/website/content/docs/security/acl/acl-migrate-tokens.mdx index 379f46e8c0b9..b09891fb483b 100644 --- a/website/content/docs/security/acl/acl-migrate-tokens.mdx +++ b/website/content/docs/security/acl/acl-migrate-tokens.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Legacy ACL Token Migration description: >- -Migrate legacy tokens when updating to Consul 1.4.0+ from earlier versions to use the current ACL system. Learn about the migration process, how to update tokens, and examples for creating policies. + Migrate legacy tokens when updating to Consul 1.4.0+ from earlier versions to use the current ACL system. Learn about the migration process, how to update tokens, and examples for creating policies. --- # ACL Token Migration diff --git a/website/content/docs/security/acl/acl-policies.mdx b/website/content/docs/security/acl/acl-policies.mdx index a317ee92ee09..25fb680387b1 100644 --- a/website/content/docs/security/acl/acl-policies.mdx +++ b/website/content/docs/security/acl/acl-policies.mdx @@ -2,7 +2,7 @@ layout: docs page_title: ACL Policies description: >- -ACL policies define access control rules for resources in Consul. When an ACL token is submitted with a request, Consul authorizes access based on the token's associated policies. Learn how to format and combine rules into policies and apply them to tokens. + ACL policies define access control rules for resources in Consul. When an ACL token is submitted with a request, Consul authorizes access based on the token's associated policies. Learn how to format and combine rules into policies and apply them to tokens. --- # ACL Policies diff --git a/website/content/docs/security/acl/acl-roles.mdx b/website/content/docs/security/acl/acl-roles.mdx index 57c3912c8a8f..377c69c933f5 100644 --- a/website/content/docs/security/acl/acl-roles.mdx +++ b/website/content/docs/security/acl/acl-roles.mdx @@ -2,7 +2,7 @@ layout: docs page_title: ACL Roles description: >- -Roles are a named collection of ACL policies, service identities, and node identities. Learn how roles allow you to reuse and update access control policies without needing to distribute new tokens to users. + Roles are a named collection of ACL policies, service identities, and node identities. Learn how roles allow you to reuse and update access control policies without needing to distribute new tokens to users. --- # ACL Roles diff --git a/website/content/docs/security/acl/acl-rules.mdx b/website/content/docs/security/acl/acl-rules.mdx index 5a6fa1dc3744..17314b962767 100644 --- a/website/content/docs/security/acl/acl-rules.mdx +++ b/website/content/docs/security/acl/acl-rules.mdx @@ -2,7 +2,7 @@ layout: docs page_title: ACL Rules description: >- -Rules define read, write, and deny access controls for datacenter resources. Learn about these resources and how to assign rules to them, as well as their restrictions and API interactions. + Rules define read, write, and deny access controls for datacenter resources. Learn about these resources and how to assign rules to them, as well as their restrictions and API interactions. --- # ACL Rules diff --git a/website/content/docs/security/acl/acl-tokens.mdx b/website/content/docs/security/acl/acl-tokens.mdx index 1171964424d9..319992c48572 100644 --- a/website/content/docs/security/acl/acl-tokens.mdx +++ b/website/content/docs/security/acl/acl-tokens.mdx @@ -2,7 +2,7 @@ layout: docs page_title: ACL Tokens description: >- -Tokens are used to authenticate users, services, and agents and authorize their access to resources in Consul. Learn about token attributes, special-purpose and built-in tokens, and how to pass a token’s SecretID in the CLI and API. + Tokens are used to authenticate users, services, and agents and authorize their access to resources in Consul. Learn about token attributes, special-purpose and built-in tokens, and how to pass a token’s SecretID in the CLI and API. --- # ACL Tokens diff --git a/website/content/docs/security/acl/index.mdx b/website/content/docs/security/acl/index.mdx index e4229abdce5c..aadda50894ef 100644 --- a/website/content/docs/security/acl/index.mdx +++ b/website/content/docs/security/acl/index.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Access Control List (ACL): Overview +page_title: Access Control List (ACL) - Overview description: >- -Consul's ACL system secures communication and controls access to the API, CLI, and UI. Learn about ACL components and how they interact to authenticate requests and authorize access for your network. + Consul's ACL system secures communication and controls access to the API, CLI, and UI. Learn about ACL components and how they interact to authenticate requests and authorize access for your network. --- # Access Control List (ACL) Overview diff --git a/website/content/docs/security/encryption.mdx b/website/content/docs/security/encryption.mdx index 891918c81d8a..99f2b12a825b 100644 --- a/website/content/docs/security/encryption.mdx +++ b/website/content/docs/security/encryption.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Encryption Systems description: >- -Consul supports encrypting all of its network traffic. Remote Process Calls (RPCs) between client and server agents can be encrypted with TLS and authenticated with certificates. Gossip communication between all agents can also be encrypted. + Consul supports encrypting all of its network traffic. Remote Process Calls (RPCs) between client and server agents can be encrypted with TLS and authenticated with certificates. Gossip communication between all agents can also be encrypted. --- # Encryption diff --git a/website/content/docs/security/index.mdx b/website/content/docs/security/index.mdx index ef5e80d3f05f..346d0ec59103 100644 --- a/website/content/docs/security/index.mdx +++ b/website/content/docs/security/index.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Security: Overview +page_title: Security - Overview description: >- -Security requirements and recommendations for Consul vary depending on workloads and environments. Learn how ACLs and encryption can protect access to and communication within your datacenter. + Security requirements and recommendations for Consul vary depending on workloads and environments. Learn how ACLs and encryption can protect access to and communication within your datacenter. --- ## Security Models diff --git a/website/content/docs/security/security-models/core.mdx b/website/content/docs/security/security-models/core.mdx index 3ec43f8bafac..af411aed674f 100644 --- a/website/content/docs/security/security-models/core.mdx +++ b/website/content/docs/security/security-models/core.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Security Models: Consul +page_title: Security Models - Consul description: >- -The security model for Consul Core details requirements and recommendations for securing your deployment of Consul. Learn about potential threats and how to protect Consul from malicious actors. + The security model for Consul Core details requirements and recommendations for securing your deployment of Consul. Learn about potential threats and how to protect Consul from malicious actors. --- ## Overview diff --git a/website/content/docs/security/security-models/index.mdx b/website/content/docs/security/security-models/index.mdx index abf86f186304..be6b3978b40d 100644 --- a/website/content/docs/security/security-models/index.mdx +++ b/website/content/docs/security/security-models/index.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Security Models: Overview +page_title: Security Models - Overview description: >- -Security models are the set of requirements and recommendations for securely operating a Consul deployment. Learn about security models and how they differ between environments. + Security models are the set of requirements and recommendations for securely operating a Consul deployment. Learn about security models and how they differ between environments. --- ## Overview diff --git a/website/content/docs/security/security-models/nia.mdx b/website/content/docs/security/security-models/nia.mdx index b9117be0d73e..b53949d6cb24 100644 --- a/website/content/docs/security/security-models/nia.mdx +++ b/website/content/docs/security/security-models/nia.mdx @@ -1,8 +1,8 @@ --- layout: docs -page_title: Security Models: Network Infrastructure Automation (NIA) +page_title: Security Models - Network Infrastructure Automation (NIA) description: >- -The NIA security model details requirements and recommendations for securing your Consul-Terraform-Sync (CTS) deployment. Learn about potential threats and how to protect CTS from malicious actors. + The NIA security model details requirements and recommendations for securing your Consul-Terraform-Sync (CTS) deployment. Learn about potential threats and how to protect CTS from malicious actors. --- ## Overview diff --git a/website/content/docs/troubleshoot/common-errors.mdx b/website/content/docs/troubleshoot/common-errors.mdx index 0894e5d834e3..ad8f60be7cf2 100644 --- a/website/content/docs/troubleshoot/common-errors.mdx +++ b/website/content/docs/troubleshoot/common-errors.mdx @@ -2,7 +2,7 @@ layout: docs 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. + 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. --- # Common Error Messages diff --git a/website/content/docs/troubleshoot/faq.mdx b/website/content/docs/troubleshoot/faq.mdx index 7d3c5d191a70..d81c506e94a5 100644 --- a/website/content/docs/troubleshoot/faq.mdx +++ b/website/content/docs/troubleshoot/faq.mdx @@ -2,7 +2,7 @@ layout: docs 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. + 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. --- # Frequently Asked Questions