Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix typos and update ecs compat table #18215

Merged
merged 4 commits into from
Jul 21, 2023
Merged

fix typos and update ecs compat table #18215

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
216f793
fix typos and update ecs compat table
trujillo-adam Jul 20, 2023
1df0326
real info for the ecs compat matrix table
trujillo-adam Jul 20, 2023
12df6a1
Update website/content/docs/ecs/compatibility.mdx
trujillo-adam Jul 21, 2023
5eb12fc
Merge branch 'main' into docs/fix-formatting-cts-ha-usage
trujillo-adam Jul 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 7 additions & 8 deletions website/content/docs/ecs/compatibility.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,19 +5,18 @@ 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.
---

# Consul on AWS Elastic Container Service (ECS) Compatability Matrix
# 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.5.2 binary must use the `consul-ecs` 0.5.2 Terraform module.

## Supported Consul versions

| Consul Version | Compatible consul-ecs Versions |
| -------------- | ------------------------------- |
| 1.14.x | 0.5.2+ |
| 1.13.x | 0.5.2+ |
| 1.12.x | 0.5.x |
| 1.11.x | 0.3.0, 0.4.x |
| 1.10.x | 0.2.x |
| Consul Version | Compatible consul-ecs Version |
|----------------------- | ----------------------------- |
| 1.15.x, 1.14.x, 1.13.x | 0.6.x |
| 1.14.x, 1.13.x, 1.12.x | 0.5.2+ |
| 1.11.x | 0.3.0, 0.4.x |
| 1.10.x | 0.2.x |


## Supported Envoy versions
Expand Down
4 changes: 2 additions & 2 deletions website/content/docs/lambda/registration/automate.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
---
layout: docs
page_title: Automate Lambda Function Registeration
page_title: Automate Lambda function registration
description: >-
Register AWS Lambda functions with Consul service mesh using the Consul Lambda registrator. The Consul Lambda registrator automates Lambda function registration.
---

# Automate Lambda Function Registeration
# Automate Lambda function registration

This topic describes how to automate Lambda function registration using Consul's Lambda registrator module for Terraform.

Expand Down
14 changes: 8 additions & 6 deletions website/content/docs/nia/usage/run-ha.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,16 @@
---
layout: docs
page_title: Run Consul-Terraform-Sync with High Availability
page_title: Run Consul-Terraform-Sync with high availability
description: >-
Improve network automation resiliency by enabling high availability for Consul-Terraform-Sync. HA enables persistent task and event data so that CTS functions as expected during a failover event.
---

# Run Consul-Terraform-Sync with High Availability
# Run Consul-Terraform-Sync with high availability

<EnterpriseAlert>
Licenses are only required for Consul-Terraform-Sync (CTS) Enterprise
An enterpise license is only required for enterprise distributions of Consul-Terraform-Sync (CTS).
</EnterpriseAlert>

This topic describes how to run Consul-Terraform-Sync (CTS) configured for high availability. High availability is an enterprise capability that ensures that all changes to Consul that occur during a failover transition are processed and that CTS continues to operate as expected.

## Introduction
Expand Down Expand Up @@ -120,9 +122,9 @@ When high availability is enabled, CTS persists task and event data. Refer to [S

You can use the following methods for modifying tasks when high availability is enabled. We recommend choosing a single method to make all task configuration changes because inconsistencies between the state and the configuration can occur when mixing methods.

### Delete and recreate the task (recommended)
### Delete and recreate the task

Use the CTS API to identify the CTS leader instance as well as delete and replace a task.
We recommend deleting and recreating a task if you need to make a modification. Use the CTS API to identify the CTS leader instance and replace a task.

1. Identify the leader CTS instance by either making a call to the [`status/cluster` API endpoint](/consul/docs/nia/api/status#cluster-status) or by checking the logs for the following entry:

Expand All @@ -143,7 +145,7 @@ Use the CTS API to identify the CTS leader instance as well as delete and replac
--request POST \
--data @payload.json \
localhost:8558/v1/tasks
```
```

You can also use the [`task-create` command](/consul/docs/nia/cli/task#task-create) to complete this step.

Expand Down