From 711a05d3ce900e2156ce462900f4507a0cb02c4b Mon Sep 17 00:00:00 2001 From: Michael Schurter Date: Fri, 14 May 2021 10:45:12 -0700 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Seth Hoenig --- website/content/docs/drivers/remote/ecs.mdx | 4 ++-- website/content/docs/drivers/remote/index.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/website/content/docs/drivers/remote/ecs.mdx b/website/content/docs/drivers/remote/ecs.mdx index 6a163431b..948970b48 100644 --- a/website/content/docs/drivers/remote/ecs.mdx +++ b/website/content/docs/drivers/remote/ecs.mdx @@ -16,7 +16,7 @@ intended for production use.** The ECS task driver plugin for Nomad allows running [AWS ECS][ecs] tasks via Nomad. Allocations for these jobs are scheduled onto Nomad clients like -traditional task drivers, however the actual task code in executed remotely in +traditional task drivers, however the actual task is executed remotely in AWS ECS. The Nomad client agent manages the remote ECS task like any other local Nomad task: restarting it if it fails, stopping it when requested, etc. @@ -104,7 +104,7 @@ job "nomad-ecs-demo" { - `config.task` stanza defines the configuration of the ECS task: - `launch_type` - The launch type on which to run your task. - - `task_definition` - The family and revision (family:revision) or full ARN + - `task_definition` - The family and revision (`family:revision`) or full ARN of the task definition to run. - `network_configuration` - The network configuration for the task (eg `awsvpc` for `FARGATE` tasks). diff --git a/website/content/docs/drivers/remote/index.mdx b/website/content/docs/drivers/remote/index.mdx index 30662598a..ebec5fb31 100644 --- a/website/content/docs/drivers/remote/index.mdx +++ b/website/content/docs/drivers/remote/index.mdx @@ -15,7 +15,7 @@ incompatible changes between Nomad releases or deprecation. Please refer to the ~> **Known Bugs:** When a Nomad node running a remote task driver goes down, another node must be available and able to run the replacement allocation in order to take advantage of remote task driver's ability to avoid restarting -lost tasks. If a new node is not immediately available but made started later, +lost tasks. If a new node is not immediately available but started later, it will start a new instance of the remote task instead of reconnecting to the old one. Follow [#10592][gh-10592] for the fix.