Merge pull request #14746 from hashicorp/docs/search-refresh06
docs: Search Description Refresh Batch 06
This commit is contained in:
Jeff Boruszak
GitHub
commit
0f95b266be
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul API Gateway Gateway
|
||||
description: >-
|
||||
This topic describes how to configure the Consul API Gateway Gateway object
|
||||
page_title: Gateway Resource Configuration
|
||||
description: >-
|
||||
Learn how to configure the `Gateway` resource to define how the Consul API Gateway handles incoming service mesh traffic with this configuration model and reference specifications.
|
||||
---
|
||||
|
||||
# Gateway
|
||||
# Gateway Resource Configuration
|
||||
|
||||
This topic provides full details about the `Gateway` resource.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul API Gateway GatewayClass
|
||||
description: >-
|
||||
Consul API Gateway GatewayClass
|
||||
page_title: GatewayClass Resource Configuration
|
||||
description: >-
|
||||
A `GatewayClass` resource specifies a controller name, controller parameters, and global `Gateway` options for Consul API Gateway. Learn about its configuration model and reference specifications, and review an example configuration.
|
||||
---
|
||||
|
||||
# GatewayClass
|
||||
# GatewayClass Resource Configuration
|
||||
|
||||
This topic provides describes how to configure the `GatewayClass` resource, a generic Kubernetes gateway object used as a template for creating `Gateway` resources.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul API Gateway GatewayClassConfig
|
||||
description: >-
|
||||
Consul API Gateway GatewayClassConfig
|
||||
page_title: GatewayClassConfig Resource Configuration
|
||||
description: >-
|
||||
The `GatewayClassConfig` resource specifies connection information and settings that Consul API Gateway uses to connect to Consul. Learn about its configuration model and reference specifications, and review an example configuration.
|
||||
---
|
||||
|
||||
# GatewayClassConfig
|
||||
# GatewayClassConfig Resource Configuration
|
||||
|
||||
This topic provides full details about the `GatewayClassConfig` resource.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul API Gateway Configuration
|
||||
description: >-
|
||||
Consul API Gateway Configuration
|
||||
page_title: Consul API Gateway Configuration - Overview
|
||||
description: >-
|
||||
Configure your Consul API Gateway to manage traffic into your service mesh. Learn about the Kubernetes Gateway Specification items you can configure and how to configure custom API Gateways.
|
||||
---
|
||||
|
||||
# Configuration
|
||||
# Consul API Gateway Configuration Overview
|
||||
|
||||
This topic provides an overview of the configuration items that enable Consul API Gateway to manage traffic into your Consul service mesh.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul API Gateway MeshService
|
||||
description: >-
|
||||
This topic describes how to configure the Consul API Gateway MeshService object
|
||||
page_title: MeshService Resource Configuration
|
||||
description: >-
|
||||
The `MeshService` resource specifies a service running outside the Kubernetes cluster but in the same datacenter where the Consul API Gateway is deployed. Learn about its configuration model and reference specifications.
|
||||
---
|
||||
|
||||
# MeshService
|
||||
# MeshService Resource Configuration
|
||||
|
||||
This topic provides full details about the `MeshService` resource.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
"---
|
||||
layout: docs
|
||||
page_title: Consul API Gateway Routes
|
||||
description: >-
|
||||
Consul API Gateway Routes
|
||||
page_title: Route Resource Configuration
|
||||
description: >-
|
||||
The `HTTPRoute` and `TCPRoute` resources define Consul API Gateway routing behavior for traffic into the service mesh according to rules. Learn about its configuration model and reference specifications, and review an example configuration.
|
||||
---
|
||||
|
||||
# Route
|
||||
# Route Resource Configuration
|
||||
|
||||
This topic describes how to create and configure `Route` resources. Routes are independent configuration objects that are associated with specific listeners.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul API Gateway Overview
|
||||
description: >-
|
||||
Using Consul API gateway functionality
|
||||
description: >-
|
||||
Consul API Gateway enables external network client access to a service mesh on Kubernetes and forwards requests based on path or header information. Learn about how the k8s Gateway API specification configures Consul API Gateway so you can control access and simplify traffic management.
|
||||
---
|
||||
|
||||
# Consul API Gateway Overview
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Install Consul API Gateway
|
||||
description: >-
|
||||
Installing Consul API Gateway
|
||||
description: >-
|
||||
Learn how to install custom resource definitions (CRDs) and configure the Helm chart so that you can run Consul API Gateway on your Kubernetes deployment.
|
||||
---
|
||||
|
||||
# Install Consul API Gateway
|
||||
|
|
|
|||
|
|
@ -2,10 +2,10 @@
|
|||
layout: docs
|
||||
page_title: Consul API Gateway Technical Specifications
|
||||
description: >-
|
||||
This topic describes technical specifications for Consul API Gateway.
|
||||
Consul API Gateway is a service mesh add-on for Kubernetes deployments. Learn about its requirements for system resources, ports, and component versions, its Enterprise limitations, and compatible k8s cloud environments.
|
||||
---
|
||||
|
||||
# Technical Specifications
|
||||
# Consul API Gateway Technical Specifications
|
||||
|
||||
This topic describes the technical specifications associated with using Consul API Gateway.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Upgrades
|
||||
page_title: Upgrade Consul API Gateway
|
||||
description: >-
|
||||
This topic describes how to upgrade Consul API Gateway.
|
||||
Upgrade Consul API Gateway to use newly supported features. Learn about the requirements, procedures, and post-configuration changes involved in standard and specific version upgrades.
|
||||
---
|
||||
|
||||
# Upgrades
|
||||
# Upgrade Consul API Gateway
|
||||
|
||||
This topic describes how to upgrade Consul API Gateway.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul API Gateway Basic Usage
|
||||
description: >-
|
||||
This topic describes how to use Consul API Gateway.
|
||||
page_title: Use Consul API Gateway
|
||||
description: >-
|
||||
Learn how to apply a configured Consul API Gateway to your Kubernetes cluster, review the required fields for rerouting HTTP requests, and troubleshoot an error message.
|
||||
---
|
||||
|
||||
|
||||
# Usage
|
||||
# Use Consul API Gateway
|
||||
|
||||
This topic describes how to use Consul API Gateway.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul KV
|
||||
description: Consul KV is a core feature of Consul and is installed with the Consul agent.
|
||||
page_title: Key/Value (KV) Store Overview
|
||||
description: >-
|
||||
Consul includes a KV store for indexed objects, configuration parameters, and metadata that you can use to dynamically configure apps. Learn about accessing and using the KV store to extend Consul's functionality through watches, sessions, and Consul Template.
|
||||
---
|
||||
|
||||
# Consul KV
|
||||
# Key/Value (KV) Store Overview
|
||||
|
||||
Consul KV is a core feature of Consul and is installed with the Consul agent.
|
||||
Once installed with the agent, it will have reasonable defaults. Consul KV allows
|
||||
|
|
|
|||
|
|
@ -1,14 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Sessions
|
||||
page_title: Sessions and Distributed Locks Overview
|
||||
description: >-
|
||||
Consul provides a session mechanism which can be used to build distributed
|
||||
locks. Sessions act as a binding layer between nodes, health checks, and
|
||||
key/value data. They are designed to provide granular locking and are heavily
|
||||
inspired by The Chubby Lock Service for Loosely-Coupled Distributed Systems.
|
||||
Consul supports sessions that you can use to build distributed locks with granular locking. Learn about sessions, how they can prevent ""split-brain"" systems by ensuring consistency in deployments, and how they can integrate with the key/value (KV) store.
|
||||
---
|
||||
|
||||
# Sessions
|
||||
# Sessions and Distributed Locks Overview
|
||||
|
||||
Consul provides a session mechanism which can be used to build distributed locks.
|
||||
Sessions act as a binding layer between nodes, health checks, and key/value data.
|
||||
|
|
|
|||
|
|
@ -1,15 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Watches
|
||||
page_title: Watches Overview and Reference
|
||||
description: >-
|
||||
Watches are a way of specifying a view of data (e.g. list of nodes, KV pairs,
|
||||
health checks) which is monitored for updates. When an update is detected, an
|
||||
external handler is invoked. A handler can be any executable. As an example,
|
||||
you could watch the status of health checks and notify an external system when
|
||||
a check is critical.
|
||||
Watches monitor the key/value (KV) store, services, nodes, health checks, and events for updates. When a watch detects a change, it invokes a handler that can call an HTTP endpoint or run an executable. Learn how to configure watches to dynamically respond to changes in Consul.
|
||||
---
|
||||
|
||||
# Watches
|
||||
# Watches Overview and Reference
|
||||
|
||||
Watches are a way of specifying a view of data (e.g. list of nodes, KV pairs, health
|
||||
checks) which is monitored for updates. When an update is detected, an external handler
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Architecture - AWS ECS
|
||||
page_title: Consul on AWS Elastic Container Service (ECS) Architecture
|
||||
description: >-
|
||||
Architecture of Consul Service Mesh on AWS ECS (Elastic Container Service).
|
||||
Consul's architecture supports Amazon Web Services ECS deployments. Learn about how the two work together, including the order tasks and containers startup and shutdown, as well as requirements for the AWS IAM auth method, the ACL controller and tokens, and health check syncing.
|
||||
---
|
||||
|
||||
# Architecture
|
||||
# Consul on AWS Elastic Container Service (ECS) Architecture
|
||||
|
||||
The following diagram shows the main components of the Consul architecture when deployed to an ECS cluster:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Compatibility Matrix
|
||||
description: Compatibility Matrix for Consul ECS
|
||||
page_title: Consul on AWS Elastic Container Service (ECS) Compatability Matrix
|
||||
description: >-
|
||||
The binary for Consul on Amazon Web Services ECS and the Terraform modules for automating deployments are tightly coupled and have specific version requirements. Review compatibility information for versions of Consul and `consul-ecs` to help you choose compatible versions.
|
||||
---
|
||||
|
||||
# Compatibility Matrix for Consul on ECS
|
||||
# Consul on AWS Elastic Container Service (ECS) Compatability Matrix
|
||||
|
||||
For every release of Consul on ECS, the `consul-ecs` binary and `consul-ecs` Terraform module are updated. The versions of the Terraform module and binary are tightly coupled. For example, `consul-ecs` 0.4.1 binary must use the `consul-ecs` 0.4.1 Terraform module.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: AWS ECS
|
||||
page_title: Consul on AWS Elastic Container Service (ECS) Configuration Reference
|
||||
description: >-
|
||||
Configuration Reference for Consul on AWS ECS (Elastic Container Service).
|
||||
Do not modify by hand! This is automatically generated documentation.
|
||||
Use the `consul-ecs` reference guide to manually configure Consul for deployment on Amazon Web Services ECS. Learn how the configuration values correspond to Terraform module input variables and review JSON configuration models for `consulLogin`, `gateway`, `proxy`, and `service` fields.
|
||||
---
|
||||
|
||||
# Configuration Reference
|
||||
# Consul on AWS Elastic Container Service (ECS) Configuration Reference
|
||||
|
||||
This pages details the configuration options for the JSON config format used
|
||||
by the `consul-ecs` binary. This configuration is passed to the `consul-ecs`
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul Enterprise - AWS ECS
|
||||
page_title: Consul Enterprise on AWS Elastic Container Service (ECS)
|
||||
description: >-
|
||||
Consul Enterprise support for Consul on ECS.
|
||||
You can deploy Consul Enterprise on Amazon Web Services ECS with an official Docker image. Learn about supported Enterprise features, including requirements for admin partitions, namespaces, and audit logging.
|
||||
---
|
||||
|
||||
# Consul Enterprise
|
||||
# Consul Enterprise on AWS Elastic Container Service (ECS)
|
||||
|
||||
You can run Consul Enterprise on ECS by specifying the Consul Enterprise Docker image in the Terraform module parameters.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: AWS ECS
|
||||
page_title: Consul on AWS Elastic Container Service (ECS) Overview
|
||||
description: >-
|
||||
Consul Service Mesh can be deployed on AWS ECS (Elastic Container Service).
|
||||
This section documents the official installation of Consul on ECS.
|
||||
Consul's architecture adapts to Amazon Web Services ECS by running each task with an application container, a client agent, and an Envoy proxy. Learn how Consul service mesh works on ECS and find getting started tutorials for several scenarios.
|
||||
---
|
||||
|
||||
# AWS ECS
|
||||
# Consul on AWS Elastic Container Service (ECS) Overview
|
||||
|
||||
You can deploy Consul service mesh applications to [AWS Elastic Container Service](https://aws.amazon.com/ecs/) (ECS) using either our official [Terraform modules](/docs/ecs/terraform/install) or by [manually configuring the task definition](/docs/ecs/manual/install).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: ACL Controller - AWS ECS
|
||||
page_title: ACL Controller Manual Installation - Consul on AWS Elastic Container Service (ECS)
|
||||
description: >-
|
||||
Manual Deployment of the ACL Controller for Consul Service Mesh on AWS ECS (Elastic Container Service).
|
||||
An ACL Controller is required to configure the AWS IAM auth method on Amazon Web Services ECS. Learn how to manually install ACL controllers by defining a task and a service and then configuring role policies.
|
||||
---
|
||||
|
||||
# Install the ACL Controller
|
||||
# Manual Installation of ACL Controller for Consul on AWS Elastic Container Service (ECS)
|
||||
|
||||
This topic describes how to manually deploy the ACL controller, which will automatically configure the [AWS IAM Auth Method](/docs/security/acl/auth-methods/aws-iam). If you are using Terraform, refer to the [Terraform Secure Configuration](/docs/ecs/terraform/secure-configuration) page to deploy the ACL controller.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Manual Installation - AWS ECS
|
||||
page_title: Install Manually - Consul on AWS Elastic Container Service (ECS)
|
||||
description: >-
|
||||
Manually Install Consul Service Mesh on AWS ECS (Elastic Container Service).
|
||||
Manually install Consul on Amazon Web Services ECS by using the Docker `consul-ecs` image to create task definitions that include required containers. Learn how to configure task definitions with example configurations.
|
||||
---
|
||||
|
||||
# Manual Installation
|
||||
# Manual Installation of Consul on AWS Elastic Container Service (ECS)
|
||||
|
||||
The following instructions describe how to use the [`consul-ecs` Docker image](https://gallery.ecr.aws/hashicorp/consul-ecs) to manually create the ECS task definition without Terraform. If you prefer to use Terraform, refer to [Consul ECS Terraform module](/docs/ecs/terraform/install).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Secure Configuration - AWS ECS
|
||||
page_title: Manual Secure Configuration - Consul on AWS Elastic Container Service (ECS)
|
||||
description: >-
|
||||
Manual Secure Configuration of the Consul Service Mesh on AWS ECS (Elastic Container Service).
|
||||
Securely configure Consul Service Mesh on Amazon Web Services ECS to protect the communication of sensitive data in production workloads. Learn how to manually configure auth methods to create tokens for clients and services and then apply tokens by role or policy.
|
||||
---
|
||||
|
||||
# Secure Configuration
|
||||
# Manual Secure Configuration of Consul on AWS Elastic Container Service (ECS)
|
||||
|
||||
This topic describes how to enable Consul security features for your production workloads.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Requirements - AWS ECS
|
||||
page_title: Requirements - Consul on AWS Elastic Container Service (ECS)
|
||||
description: >-
|
||||
Requirements for Consul Service Mesh on AWS ECS (Elastic Container Service).
|
||||
Consul has requirements to install and run on Amazon Web Services ECS. Learn about Consul's requirements for Fargate and EC2, including network mode and subnet information, as well as server, routing, and ACL controller considerations to keep in mind.
|
||||
---
|
||||
|
||||
# Requirements
|
||||
# Requirements for Consul on AWS Elastic Container Service (ECS)
|
||||
|
||||
The following requirements must be met in order to install Consul on ECS:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Resource Usage - AWS ECS
|
||||
page_title: Resource Usage - Consul on AWS Elastic Container Service (ECS)
|
||||
description: >-
|
||||
Resource usage of the Consul Service Mesh on AWS ECS (Elastic Container Service).
|
||||
Learn about the CPU and memory resources Consul uses while running on Amazon Web Services ECS, including performance test procedures and results.
|
||||
---
|
||||
|
||||
# Resource Usage
|
||||
# Resource Usage for Consul on AWS Elastic Container Service (ECS)
|
||||
|
||||
We ran performance tests of Consul on ECS to determine the resource usage of
|
||||
the sidecar containers Consul on ECS injects along with the ACL controller.
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Installing Consul on AWS ECS using Terraform
|
||||
page_title: Install with Terraform - Consul on AWS Elastic Container Service (ECS)
|
||||
description: >-
|
||||
Install Consul Service Mesh on AWS ECS with Terraform (Elastic Container Service).
|
||||
When you install Consul on Amazon Web Services ECS, you can use Terraform modules to simplify the process. Learn how to create task definitions, schedule tasks for your service mesh, and configure routes with example configurations.
|
||||
---
|
||||
|
||||
# Installation with Terraform
|
||||
# Install Consul on AWS Elastic Container Service (ECS) with Terraform
|
||||
|
||||
This topic describes how to use HashiCorp's Terraform modules to launch your application in AWS ECS as part of Consul service mesh. If you do not use Terraform, refer to the [Manual Installation](/docs/ecs/manual/install) page to install Consul on ECS without Terraform.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Migrate Existing Tasks - AWS ECS
|
||||
page_title: Migrate Tasks with Terraform - Consul on AWS Elastic Container Service (ECS)
|
||||
description: >-
|
||||
Migrate Existing Tasks
|
||||
You can migrate tasks in existing Amazon Web Services ECS deployments to a service mesh deployed with Terraform. Learn how to convert a task specified as an ECS task definition into a `mesh-task` Terraform module.
|
||||
---
|
||||
|
||||
# Migrate Existing Tasks
|
||||
# Migrate Tasks to Consul on AWS Elastic Container Service (ECS) with Terraform
|
||||
|
||||
This topic describes how to migrate your existing ECS Tasks to use our [`mesh-task` Terraform module](https://registry.terraform.io/modules/hashicorp/consul-ecs/aws/latest/submodules/mesh-task).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Secure Configuration - AWS ECS
|
||||
page_title: Secure Configuration with Terraform - Consul on AWS Elastic Container Service (ECS)
|
||||
description: >-
|
||||
Secure Configuration of the Consul Service Mesh on AWS ECS (Elastic Container Service) with Terraform.
|
||||
When running Consul on Amazon Web Services ECS, you can use Terraform to secure your service mesh with an auth method and ACL controller. Learn how to configure Terraform modules to enable secure deployment.
|
||||
---
|
||||
|
||||
# Secure Configuration
|
||||
# Secure Configuration for Consul on AWS Elastic Container Service (ECS) with Terraform
|
||||
|
||||
This topic describes how to enable Consul security features for your production workloads.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul Clients Outside of Kubernetes - Kubernetes
|
||||
page_title: Join External Clients to Consul on Kubernetes
|
||||
description: >-
|
||||
Consul clients running on non-Kubernetes nodes can join a Consul cluster
|
||||
running within Kubernetes.
|
||||
Client agents running on VMs can join a Consul datacenter running on Kubernetes. Configure the Kubernetes installation to accept communication from external clients.
|
||||
---
|
||||
|
||||
# Consul Clients Outside Kubernetes
|
||||
# Join External Clients to Consul on Kubernetes
|
||||
|
||||
Consul clients running on non-Kubernetes nodes can join a Consul cluster running within Kubernetes.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul Enterprise
|
||||
description: Configuration for running Consul Enterprise
|
||||
page_title: Deploy Consul Enterprise on Kubernetes
|
||||
description: >-
|
||||
Consul Enterprise features are available when running Consul on Kubernetes. Learn how to apply your license in the Helm chart and return the license information with the `consul license get` command.
|
||||
---
|
||||
|
||||
# Consul Enterprise
|
||||
# Deploy Consul Enterprise on Kubernetes
|
||||
|
||||
You can use this Helm chart to deploy Consul Enterprise by following a few extra steps.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Multi-Cluster Federation Overview
|
||||
page_title: WAN Federation Through Mesh Gateways - Overview
|
||||
description: >-
|
||||
Installing on multiple Kubernetes clusters.
|
||||
Federating Consul datacenters through mesh gateways enables agents to engage in WAN communication across runtimes and cloud providers. Learn about multi-cluster federation and its network requirements for Consul on Kubernetes.
|
||||
---
|
||||
|
||||
# Multi-Cluster Federation Overview
|
||||
# WAN Federation Through Mesh Gateways Overview
|
||||
|
||||
In Consul, federation is the act of joining two or more Consul datacenters.
|
||||
When datacenters are joined, Consul servers in each datacenter can communicate
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Federation Between Kubernetes Clusters
|
||||
page_title: WAN Federation Through Mesh Gateways - Multiple Kubernetes Clusters
|
||||
description: >-
|
||||
Federating multiple Kubernetes clusters.
|
||||
WAN federation through mesh gateways enables federating multiple Kubernetes clusters in Consul. Learn how to configure primary and secondary datacenters, export a federation secret, get the k8s API URL, and verify federation.
|
||||
---
|
||||
|
||||
# Federation Between Kubernetes Clusters
|
||||
# WAN Federation Between Multiple Kubernetes Clusters Through Mesh Gateways
|
||||
|
||||
-> **1.8.0+:** This feature is available in Consul versions 1.8.0 and higher
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Federation Between VMs and Kubernetes
|
||||
page_title: WAN Federation Through Mesh Gateways - VMs and Kubernetes
|
||||
description: >-
|
||||
Federating Kubernetes clusters and VMs.
|
||||
WAN federation through mesh gateways extends service mesh deployments by enabling Consul on Kubernetes to securely communicate with instances on VMs. Learn how to configure multi-cluster federation with k8s as either the primary or secondary datacenter.
|
||||
---
|
||||
|
||||
# Federation Between VMs and Kubernetes
|
||||
# WAN Federation Between VMs and Kubernetes Through Mesh Gateways
|
||||
|
||||
-> **1.8.0+:** This feature is available in Consul versions 1.8.0 and higher
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul Servers Outside of Kubernetes - Kubernetes
|
||||
description: Running Consul servers outside of Kubernetes
|
||||
page_title: Join External Servers to Consul on Kubernetes
|
||||
description: >-
|
||||
Client agents that run on Kubernetes pods can join existing clusters whose server agents run outside of k8s. Learn how to expose gossip ports and bootstrap ACLs by configuring the Helm chart.
|
||||
---
|
||||
|
||||
# Consul Servers Outside of Kubernetes
|
||||
# Join External Servers to Consul on Kubernetes
|
||||
|
||||
If you have a Consul cluster already running, you can configure your
|
||||
Consul clients inside Kubernetes to join this existing cluster.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Single Consul Datacenter in Multiple Kubernetes Clusters - Kubernetes
|
||||
description: Single Consul Datacenter deployed in multiple Kubernetes clusters
|
||||
page_title: Deploy Single Consul Datacenter Across Multiple K8s Clusters
|
||||
description: >-
|
||||
A single Consul datacenter can run across multiple Kubernetes pods in a flat network as long as only one pod has server agents. Learn how to configure the Helm chart, deploy pods in sequence, and verify your service mesh.
|
||||
---
|
||||
|
||||
# Single Consul Datacenter in Multiple Kubernetes Clusters
|
||||
# Deploy Single Consul Datacenter Across Multiple Kubernetes Clusters
|
||||
|
||||
~> **Note:** When running Consul across multiple Kubernetes clusters, we recommend using [admin partitions](/docs/enterprise/admin-partitions) for production environments. This Consul Enterprise feature allows you to accommodate multiple tenants without resource collisions when administering a cluster at scale. Admin partitions also enable you to run Consul on Kubernetes clusters across a non-flat network.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: AWS Lambda
|
||||
page_title: Consul and AWS Lambda Overview
|
||||
description: >-
|
||||
Consul supports registering AWS Lambda functions as Consul services. This
|
||||
section documents the process of integrating AWS Lambda with Consul services.
|
||||
Consul supports Amazon Web Services Lambda functions, which are event-driven programs and scripts. Learn about Consul's requirements for registering and invoking AWS Lambda functions in your service mesh.
|
||||
---
|
||||
|
||||
# AWS Lambda Overview
|
||||
# Consul and AWS Lambda Overview
|
||||
|
||||
You can configure Consul to allow services in your mesh to invoke Lambda functions, as well as allow Lambda functions to invoke services in your mesh. Lambda functions are programs or scripts that run in AWS Lambda. Refer to the [AWS Lambda website](https://aws.amazon.com/lambda/) for additional information.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Invoke Lambda Functions
|
||||
page_title: Invoke AWS Lambda Functions
|
||||
description: >-
|
||||
This topic describes how to invoke AWS Lambda functions from the Consul service mesh.
|
||||
You can invoke an Amazon Web Services Lambda function in your Consul service mesh by configuring terminating gateways or sidecar proxies. Learn how to declare a registered function as an upstream and why we recommend using terminating gateways with Lambda.
|
||||
---
|
||||
|
||||
# Invoke Lambda Functions from Mesh Services
|
||||
|
|
|
|||
|
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: AWS IAM Auth Method
|
||||
page_title: AWS Identity and Access Management (IAM) Auth Method
|
||||
description: >-
|
||||
The AWS IAM auth method type allows for AWS IAM Roles and Users
|
||||
to be used to authenticate to Consul.
|
||||
Use the AWS IAM auth method to authenticate to Consul through Amazon Web Service Identity Access Management role and user identities. Learn how to configure the auth method parameters using this reference page and example configuration.
|
||||
---
|
||||
|
||||
# AWS IAM Auth Method
|
||||
# AWS Identity and Access Management (IAM) Auth Method
|
||||
|
||||
The AWS Identity and Access Management (IAM) auth method type allows for AWS
|
||||
IAM Roles and Users to be used to authenticate to Consul in order to obtain
|
||||
|
|
|
|||
|
|
@ -1,13 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: ACL Auth Methods
|
||||
page_title: Auth Methods Overview
|
||||
description: >-
|
||||
An auth method is a component in Consul that performs authentication against a
|
||||
trusted external party to authorize the creation of an ACL tokens usable
|
||||
within the local datacenter.
|
||||
An auth method enables Consul to authenticate the identity of a user or application and then automatically provision an ACL token with privileges based on identity attributes. Learn how the overall login process works and how auth methods and binding rules can help you secure your service mesh with minimal operator intervention.
|
||||
---
|
||||
|
||||
# ACL Auth Methods
|
||||
# Auth Methods Overview
|
||||
|
||||
-> **1.5.0+:** Auth methods only exist in Consul versions 1.5.0 and newer.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,14 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: JWT Auth Method
|
||||
page_title: JSON Web Token (JWT) Auth Method
|
||||
description: >-
|
||||
The JWT auth method can be used to authenticate with Consul by providing a
|
||||
JWT directly. The JWT is cryptographically verified using locally-provided
|
||||
keys, or, if configured, an OIDC Discovery service can be used to fetch the
|
||||
appropriate keys.
|
||||
Use the JWT auth method to authenticate to Consul with a JSON web token and receive an ACL token with privileges based on JWT identity attributes. Learn how to configure the auth method parameters using this reference page and example configuration.
|
||||
---
|
||||
|
||||
# JWT Auth Method
|
||||
# JSON Web Token (JWT) Auth Method
|
||||
|
||||
-> **1.8.0+:** This feature is available in Consul versions 1.8.0 and newer.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,8 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Kubernetes Auth Method
|
||||
page_title: Kubernetes Auth Method
|
||||
description: >-
|
||||
The Kubernetes auth method type allows for a Kubernetes service account token
|
||||
to be used to authenticate to Consul. This method of authentication makes it
|
||||
easy to introduce a Consul token into a Kubernetes pod.
|
||||
Use the Kubernetes auth method type to authenticate to Consul with a Kubernetes service account token and receive an ACL token with privileges based on JWT identity attributes. Learn how to configure auth method parameters using this reference page and example configuration.
|
||||
---
|
||||
|
||||
# Kubernetes Auth Method
|
||||
|
|
|
|||
|
|
@ -1,14 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: OIDC Auth Method
|
||||
page_title: OpenID Connect (OIDC) Auth Method
|
||||
description: >-
|
||||
The OIDC auth method can be used to authenticate with Consul using OpenID
|
||||
Connect (OIDC). This method allows authentication via a configured OIDC
|
||||
provider using the user's web browser. This method may be initiated from the
|
||||
Consul UI or the command line.
|
||||
Use the OIDC auth method type to authenticate to Consul through a web browser with an OpenID Connect provider. Learn how to configure the auth method parameters using this reference page and example configuration.
|
||||
---
|
||||
|
||||
# OIDC Auth Method
|
||||
# OpenID Connect (OIDC) Auth Method
|
||||
|
||||
<EnterpriseAlert>
|
||||
This feature requires version 1.8.0+ of
|
||||
|
|
|
|||
Loading…
Reference in New Issue