Merge pull request #14656 from hashicorp/docs/search-metadata-headers
docs: Search Refresh Fixes
This commit is contained in:
Jeff Boruszak
GitHub
commit
07d076a92c
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: How to Use Configuration Entries
|
page_title: How to Use Configuration Entries
|
||||||
description: >-
|
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
|
# How to Use Configuration Entries
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Agents: CLI Reference
|
page_title: Agents - CLI Reference
|
||||||
description: >-
|
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))
|
# Agents Command-line Reference ((#commandline_options))
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Agents: Configuration File Reference
|
page_title: Agents - Configuration File Reference
|
||||||
description: >-
|
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.
|
||||||
---
|
---
|
||||||
|
|
||||||
# Agents Configuration File Reference ((#configuration_files))
|
# Agents Configuration File Reference ((#configuration_files))
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Agents: Configuration Explained
|
page_title: Agents - Configuration Explained
|
||||||
description: >-
|
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
|
# Agent Configuration
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Agents Overview
|
page_title: Agents Overview
|
||||||
description: >-
|
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
|
# Agents Overview
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Legacy RPC Protocol
|
page_title: Legacy RPC Protocol
|
||||||
description: >-
|
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
|
# RPC Protocol
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Sentinel ACL Policies (Enterprise)
|
page_title: Sentinel ACL Policies (Enterprise)
|
||||||
description: >-
|
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
|
# Sentinel for KV ACL Policy Enforcement
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Agents: Enable Metrics
|
page_title: Agents - Enable Telemetry Metrics
|
||||||
description: >-
|
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
|
# Agent Telemetry
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Anti-Entropy Enforcement
|
page_title: Anti-Entropy Enforcement
|
||||||
description: >-
|
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
|
# Anti-Entropy Enforcement
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Consensus Protocol | Raft
|
page_title: Consensus Protocol | Raft
|
||||||
description: >-
|
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
|
# Consensus Protocol
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Network Coordinates
|
page_title: Network Coordinates
|
||||||
description: >-
|
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
|
# Network Coordinates
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Gossip Protocol | Serf
|
page_title: Gossip Protocol | Serf
|
||||||
description: >-
|
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
|
# Gossip Protocol
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Fault Tolerance in Consul
|
page_title: Fault Tolerance in Consul
|
||||||
description: >-
|
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
|
# Fault Tolerance
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Consul Architecture
|
page_title: Consul Architecture
|
||||||
description: >-
|
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
|
# Consul Internals Overview
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Consistency Verification | Jepsen Testing Results
|
page_title: Consistency Verification | Jepsen Testing Results
|
||||||
description: >-
|
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
|
# Jepsen Testing Results
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Discovery Explained
|
page_title: Service Discovery Explained
|
||||||
description: >-
|
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?
|
# What is service discovery?
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Explained
|
page_title: Service Mesh Explained
|
||||||
description: >-
|
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?
|
# What is a service mesh?
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Certificate Authority: AWS Certificate Manager
|
page_title: Service Mesh Certificate Authority - AWS Certificate Manager
|
||||||
description: >-
|
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
|
# AWS Certificate Manager as a Service Mesh Certificate Authority
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Certificate Authority: Built-in Service Mesh CA
|
page_title: Certificate Authority - Built-in Service Mesh CA
|
||||||
description: >-
|
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
|
# Built-In Certificate Authority for Service Mesh
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Certificate Authority: Overview
|
page_title: Service Mesh Certificate Authority - Overview
|
||||||
description: >-
|
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
|
# Service Mesh Certificate Authority Overview
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Certificate Authority: Vault
|
page_title: Service Mesh Certificate Authority - Vault
|
||||||
description: >-
|
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
|
# Vault as a Service Mesh Certificate Authority
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Cluster Peering: Create and Manage Connections
|
page_title: Cluster Peering - Create and Manage Connections
|
||||||
description: >-
|
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
|
# Create and Manage Cluster Peering Connections
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh: What is Cluster Peering?
|
page_title: Service Mesh - What is Cluster Peering?
|
||||||
description: >-
|
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?
|
# What is Cluster Peering?
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Cluster Peering on Kubernetes
|
page_title: Cluster Peering on Kubernetes
|
||||||
description: >-
|
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
|
# Cluster Peering on Kubernetes
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Exported Services: Configuration Entry Reference
|
page_title: Exported Services - Configuration Entry Reference
|
||||||
description: >-
|
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
|
# Exported Services Configuration Entry
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Configuration Entry Overview
|
page_title: Configuration Entry Overview
|
||||||
description: >-
|
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
|
# Configuration Entry Overview
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Ingress Gateway: Configuration Entry Reference
|
page_title: Ingress Gateway - Configuration Entry Reference
|
||||||
description: >-
|
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
|
# Ingress Gateway Configuration Entry
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Mesh: Configuration Entry Reference
|
page_title: Mesh - Configuration Entry Reference
|
||||||
description: >-
|
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
|
# Mesh Configuration Entry
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Proxy Defaults: Configuration Entry Reference
|
page_title: Proxy Defaults - Configuration Entry Reference
|
||||||
description: >-
|
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
|
# Proxy Defaults Configuration Entry
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Defaults: Configuration Entry Reference
|
page_title: Service Defaults - Configuration Entry Reference
|
||||||
description: >-
|
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
|
# Service Defaults Configuration Entry
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Intentions: Configuration Entry Reference
|
page_title: Service Intentions - Configuration Entry Reference
|
||||||
description: >-
|
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))
|
# Service Intentions Configuration Entry ((#service-intentions))
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Resolver: Configuration Entry Reference
|
page_title: Service Resolver - Configuration Entry Reference
|
||||||
description: >-
|
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
|
# Service Resolver Configuration Entry
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Router: Configuration Entry Reference
|
page_title: Service Router - Configuration Entry Reference
|
||||||
description: >-
|
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
|
# Service Router Configuration Entry
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Splitter: Configuration Entry Reference
|
page_title: Service Splitter - Configuration Entry Reference
|
||||||
description: >-
|
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
|
# Service Splitter Configuration Entry
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Terminating Gateway: Configuration Entry Reference
|
page_title: Terminating Gateway - Configuration Entry Reference
|
||||||
description: >-
|
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
|
# Terminating Gateway Configuration Entry
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Configuration: Overview
|
page_title: Service Mesh Configuration - Overview
|
||||||
description: >-
|
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
|
# Service Mesh Configuration Overview
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh: How it Works
|
page_title: Service Mesh - How it Works
|
||||||
description: >-
|
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 Service Mesh Works
|
# How Service Mesh Works
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Gateway Types
|
page_title: Gateway Types
|
||||||
description: >-
|
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
|
# Types of Gateway Connections in a Service Mesh
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Debugging
|
page_title: Service Mesh Debugging
|
||||||
description: >-
|
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
|
# Service Mesh Debugging
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Distributed Tracing
|
page_title: Service Mesh Distributed Tracing
|
||||||
description: >-
|
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
|
# Distributed Tracing
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Gateways Overview
|
page_title: Gateways Overview
|
||||||
description: >-
|
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
|
# Gateways Overview
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Ingress Gateway | Service Mesh
|
page_title: Ingress Gateway | Service Mesh
|
||||||
description: >-
|
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
|
# Ingress Gateways
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Mesh Gateways between Datacenters
|
page_title: Mesh Gateways between Datacenters
|
||||||
description: >-
|
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
|
# Mesh Gateways between Datacenters
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Mesh Gateways between Admin Partitions
|
page_title: Mesh Gateways between Admin Partitions
|
||||||
description: >-
|
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.
|
||||||
---
|
---
|
||||||
|
|
||||||
# Mesh Gateways between Admin Partitions
|
# Mesh Gateways between Admin Partitions
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Mesh Gateways between Peered Clusters
|
page_title: Mesh Gateways between Peered Clusters
|
||||||
description: >-
|
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
|
# Mesh Gateways between Peered Clusters
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Mesh Gateways for WAN Federation
|
page_title: Mesh Gateways for WAN Federation
|
||||||
description: >-
|
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
|
# Mesh Gateways for WAN Federation
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Terminating Gateway | Service Mesh
|
page_title: Terminating Gateway | Service Mesh
|
||||||
description: >-
|
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
|
# Terminating Gateways
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh on Consul
|
page_title: Service Mesh on Consul
|
||||||
description: >-
|
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
|
# Consul Service Mesh
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Intentions (Legacy Mode)
|
page_title: Intentions (Legacy Mode)
|
||||||
description: >-
|
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
|
# Intentions in Legacy Mode
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Intentions
|
page_title: Service Mesh Intentions
|
||||||
description: >-
|
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
|
# Service Mesh Intentions
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Traffic Management: Discovery Chain
|
page_title: Service Mesh Traffic Management - Discovery Chain
|
||||||
description: >-
|
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
|
# Discovery Chain for Service Mesh Traffic Management
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Traffic Management: Overview
|
page_title: Service Mesh Traffic Management - Overview
|
||||||
description: >-
|
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.
|
-> **1.6.0+:** This feature is available in Consul versions 1.6.0 and newer.
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Native App Integration: Go Apps
|
page_title: Service Mesh Native App Integration - Go Apps
|
||||||
description: >-
|
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
|
# Service Mesh Native Integration for Go Applications
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Native App Integration: Overview
|
page_title: Service Mesh Native App Integration - Overview
|
||||||
description: >-
|
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
|
# Service Mesh Native App Integration Overview
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Sevice Mesh: Nomad Integration
|
page_title: Sevice Mesh - Nomad Integration
|
||||||
description: >-
|
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
|
# Consul and Nomad Integration
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Observability: Overview
|
page_title: Service Mesh Observability - Overview
|
||||||
description: >-
|
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
|
# Service Mesh Observability Overview
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Observability: UI Visualization
|
page_title: Service Mesh Observability - UI Visualization
|
||||||
description: >-
|
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
|
# Service Mesh Observability: UI Visualization
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Built-in Proxy Configuration | Service Mesh
|
page_title: Built-in Proxy Configuration | Service Mesh
|
||||||
description: >-
|
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
|
# Built-in Proxy Configuration for Service Mesh
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Envoy Proxy Configuration | Service Mesh
|
page_title: Envoy Proxy Configuration | Service Mesh
|
||||||
description: >-
|
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
|
# Envoy Proxy Configuration for Service Mesh
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Proxy Overview
|
page_title: Service Mesh Proxy Overview
|
||||||
description: >-
|
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
|
# Service Mesh Proxy Overview
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Custom Proxy Configuration | Service Mesh
|
page_title: Custom Proxy Configuration | Service Mesh
|
||||||
description: >-
|
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
|
# Custom Proxy Configuration for Service Mesh
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Managed Proxy for Connect (Legacy)
|
page_title: Managed Proxy for Connect (Legacy)
|
||||||
description: >-
|
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
|
# Managed Proxy for Connect Legacy Documentation
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Proxy Registration Overview
|
page_title: Service Mesh Proxy Registration Overview
|
||||||
description: >-
|
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
|
# Service Mesh Proxy Overview
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Register a Service Mesh Proxy Outside of a Service Registration
|
page_title: Register a Service Mesh Proxy Outside of a Service Registration
|
||||||
description: >-
|
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
|
# Register a Service Mesh Proxy Outside of a Service Registration
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Register a Service Mesh Proxy in a Service Registration
|
page_title: Register a Service Mesh Proxy in a Service Registration
|
||||||
description: >-
|
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
|
# Register a Service Mesh Proxy in a Service Registration
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh Security: Best Practices
|
page_title: Service Mesh Security - Best Practices
|
||||||
description: >-
|
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
|
# Best Practices for Service Mesh Security
|
||||||
|
|
|
||||||
|
|
@ -1,8 +1,8 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Service Mesh: Enable Transparent Proxy Mode
|
page_title: Service Mesh - Enable Transparent Proxy Mode
|
||||||
description: >-
|
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
|
# Enable Transparent Proxy Mode
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Configure Health Checks
|
page_title: Configure Health Checks
|
||||||
description: >-
|
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
|
# Health Checks
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Find services with DNS
|
page_title: Find services with DNS
|
||||||
description: >-
|
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
|
# Query services with DNS
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Register Services with Service Definitions
|
page_title: Register Services with Service Definitions
|
||||||
description: >-
|
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
|
# Register Services with Service Definitions
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Admin Partitions (Enterprise)
|
page_title: Admin Partitions (Enterprise)
|
||||||
description: >-
|
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
|
# Consul Enterprise Admin Partitions
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Audit Logging (Enterprise)
|
page_title: Audit Logging (Enterprise)
|
||||||
description: >-
|
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
|
# Audit Logging
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Automated Backups (Enterprise)
|
page_title: Automated Backups (Enterprise)
|
||||||
description: >-
|
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
|
# Automated Backups
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Federated Network Areas (Enterprise)
|
page_title: Federated Network Areas (Enterprise)
|
||||||
description: >-
|
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
|
# Consul Enterprise Advanced Federation
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Consul Enterprise
|
page_title: Consul Enterprise
|
||||||
description: >-
|
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
|
# Consul Enterprise
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Enterprise License FAQ
|
page_title: Enterprise License FAQ
|
||||||
description: >-
|
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)
|
# Frequently Asked Questions (FAQ)
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Enterprise Licenses
|
page_title: Enterprise Licenses
|
||||||
description: >-
|
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
|
# Consul Enterprise License
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Namespaces (Enterprise)
|
page_title: Namespaces (Enterprise)
|
||||||
description: >-
|
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
|
# Consul Enterprise Namespaces
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Network Segments (Enterprise)
|
page_title: Network Segments (Enterprise)
|
||||||
description: >-
|
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
|
# Network Segments
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Read Replicas (Enterprise)
|
page_title: Read Replicas (Enterprise)
|
||||||
description: >-
|
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
|
# Enhanced Read Scalability with Read Replicas
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Redundancy Zones (Enterprise)
|
page_title: Redundancy Zones (Enterprise)
|
||||||
description: >-
|
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
|
# Redundancy Zones
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Sentinel in Consul (Enterprise)
|
page_title: Sentinel in Consul (Enterprise)
|
||||||
description: >-
|
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
|
# Sentinel in Consul
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Automated Upgrades (Enterprise)
|
page_title: Automated Upgrades (Enterprise)
|
||||||
description: >-
|
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
|
# Automated Upgrades
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Bootstrap a Datacenter
|
page_title: Bootstrap a Datacenter
|
||||||
description: >-
|
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
|
# Bootstrap a Datacenter
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Auto-join a Cloud Provider
|
page_title: Auto-join a Cloud Provider
|
||||||
description: >-
|
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
|
# Cloud Auto-join
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Glossary
|
page_title: Glossary
|
||||||
description: >-
|
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
|
# Consul Vocabulary
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Install Consul
|
page_title: Install Consul
|
||||||
description: >-
|
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
|
# Install Consul
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Manually Bootstrap a Datacenter
|
page_title: Manually Bootstrap a Datacenter
|
||||||
description: >-
|
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
|
# Manually Bootstrapping a Datacenter
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Server Performance Requirements
|
page_title: Server Performance Requirements
|
||||||
description: >-
|
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
|
# Server Performance
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Required Ports
|
page_title: Required Ports
|
||||||
description: >-
|
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
|
# Required Ports
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Consul Tools
|
page_title: Consul Tools
|
||||||
description: >-
|
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
|
# Download Consul Tools
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Network Infrastructure Automation (NIA) Integration Program
|
page_title: Network Infrastructure Automation (NIA) Integration Program
|
||||||
description: >-
|
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
|
# Network Infrastructure Automation Integration Program
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Consul Integration Program
|
page_title: Consul Integration Program
|
||||||
description: >-
|
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
|
# Consul Integration Program
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Internals Overview
|
page_title: Internals Overview
|
||||||
description: >-
|
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
|
# Consul Internals Overview
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Annotations and Labels
|
page_title: Annotations and Labels
|
||||||
description: >-
|
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
|
# Annotations and Labels
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Consul on Kubernetes Control Plane Architecture
|
page_title: Consul on Kubernetes Control Plane Architecture
|
||||||
description: >-
|
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.
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Consul on Kubernetes Version Compatibility
|
page_title: Consul on Kubernetes Version Compatibility
|
||||||
description: >-
|
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
|
# Consul on Kubernetes Version Compatibility
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Configure Certificate Authority (CA) for Consul on Kubernetes
|
page_title: Configure Certificate Authority (CA) for Consul on Kubernetes
|
||||||
description: >-
|
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
|
# Configure Certificate Authority (CA) for Consul on Kubernetes
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: Configure Health Checks for Consul on Kubernetes
|
page_title: Configure Health Checks for Consul on Kubernetes
|
||||||
description: >-
|
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
|
# Configure Health Checks for Consul on Kubernetes
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: How does Consul Service Mesh Work on Kubernetes?
|
page_title: How does Consul Service Mesh Work on Kubernetes?
|
||||||
description: >-
|
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.
|
||||||
---
|
---
|
||||||
|
|
||||||
# How does Consul Service Mesh Work on Kubernetes?
|
# How does Consul Service Mesh Work on Kubernetes?
|
||||||
|
|
|
||||||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue