Skip to content

Commit 2fa045a

Browse files
Backport of docs: clarify namespace support in autoscaler (#26342)
Co-authored-by: Tim Gross <[email protected]>
1 parent 1ef5d75 commit 2fa045a

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

website/content/tools/autoscaling/agent.mdx

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,12 @@ multiple configuration files or directories to configure the agent.
1313

1414
## Nomad Namespaces
1515

16-
The Nomad Autoscaler currently has limited support for
17-
[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
18-
specifying a namespace; if configured with a namespace, the Autoscaler will
19-
retrieve scaling policies and perform autoscaling only for jobs in that
20-
namespace. If the special wildcard namespace value `*` is used, the Autoscaler
21-
agent will retrieve scaling policies from all namespaces. A future version will
22-
include support for multiple namespaces.
16+
You can configure Nomad Autoscaler to use a [Nomad namespace][nomad_namespaces]
17+
using the agent's [`nomad`][autoscaler_agent_nomad] configuration block. The
18+
Autoscaler retrieves scaling policies and perform autoscaling only for jobs in
19+
that namespace. If you use the special wildcard namespace value `*`, the
20+
Autoscaler agent retrieves scaling policies from all namespaces. A future
21+
version will include support for multiple namespaces.
2322

2423
## Nomad ACLs
2524

0 commit comments

Comments
 (0)