# namespace

The get namespace command retrieves a list of all namespaces in the Kubernetes cluster. This command provides details such as namespace names, statuses, and resource quotas.

## Usage

```
cldkctl get namespace [flags]
```

## Steps

Follow the steps below to run and view the result of this command:

1. Open your terminal in the directory containing the cldkctl binary.
2. Run the following command in your terminal:

```
cldkctl get namespace
```

3. The command displays a table containing all existing namespaces and their creation dates.

<figure><img src="/files/Qx3lvL2tdtMuKaFkzspi" alt=""><figcaption></figcaption></figure>

| Column     | Description                                                   |
| ---------- | ------------------------------------------------------------- |
| Namespace  | Displays the name of each namespace available in the cluster. |
| Created At | Shows the date when the namespace was created in the cluster. |

## Flags

{% hint style="info" %}
This command supports [global flags](/guidance-for-individual/cloudeka-api-list/global-flags.md). Refer to the Global Flags section for details
{% endhint %}

| Flag       | Description                     |
| ---------- | ------------------------------- |
| -h, --help | Help for get namespace command. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudeka.ai/guidance-for-individual/cloudeka-api-list/command-reference/cldkctl-get/namespace.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.