mirror of
https://github.com/kemko/nomad.git
synced 2026-01-08 11:25:41 +03:00
Add structs and fields to support the Nomad Pools Governance Enterprise feature of controlling node pool access via namespaces. Nomad Enterprise allows users to specify a default node pool to be used by jobs that don't specify one. In order to accomplish this, it's necessary to distinguish between a job that explicitly uses the `default` node pool and one that did not specify any. If the `default` node pool is set during job canonicalization it's impossible to do this, so this commit allows a job to have an empty node pool value during registration but sets to `default` at the admission controller mutator. In order to guarantee state consistency the state store validates that the job node pool is set and exists before inserting it.
44 lines
991 B
Plaintext
44 lines
991 B
Plaintext
---
|
|
layout: docs
|
|
page_title: 'Commands: namespace delete'
|
|
description: |
|
|
The namespace delete command is used to delete a namespace.
|
|
---
|
|
|
|
# Command: namespace delete
|
|
|
|
The `namespace delete` command is used delete a namespace.
|
|
|
|
<Tip>
|
|
Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
|
|
Nomad Namespaces tutorial
|
|
</a> for more information.
|
|
</Tip>
|
|
|
|
## Usage
|
|
|
|
```plaintext
|
|
nomad namespace delete [options] <namespace>
|
|
```
|
|
|
|
The `namespace delete` command requires the name of the namespace to be deleted.
|
|
|
|
If ACLs are enabled, this command requires a management ACL token.
|
|
|
|
You cannot delete a namespace that has non-terminal jobs. In federated clusters,
|
|
you cannot delete a namespace that has non-terminal jobs in any of the federated
|
|
regions.
|
|
|
|
## General Options
|
|
|
|
@include 'general_options_no_namespace.mdx'
|
|
|
|
## Examples
|
|
|
|
Delete a namespace
|
|
|
|
```shell-session
|
|
$ nomad namespace delete api-prod
|
|
Successfully deleted namespace "api-prod"!
|
|
```
|