# Add a new namespace

From the menu select **Namespaces** then click **Add with form**.

{% hint style="info" %}
Namespaces can also be added [using a manifest](/user/kubernetes/applications/manifest.md) by clicking **Create from manifest**.
{% endhint %}

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

Give the namespace a descriptive **name**. As an optional step you can add annotations to your namespace as required by clicking **Add annotation** and filling in the **Key** and **Value** fields.

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

### Resource quota

You can assign a quota by toggling **Resource assignment** on, then setting resource limits like how much memory and CPU will be assigned.

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

### Load balancers

To set a maximum number of external load balancers that can be created inside the namespace, toggle on **Load Balancer quota** and set the **Max Load Balancers** number. If Load Balancer quota is enabled and the Max Load Balancers value is set to `0`, the use of external load balancers is effectively disabled in the namespace.

{% hint style="info" %}
This section is only visible when **Allow users to use external load balancers** is enabled in the [Cluster Setup](/user/kubernetes/cluster/setup.md#allow-users-to-use-external-load-balancer).
{% endhint %}

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

### Networking - Ingresses

This section lets you define which ingress controllers are allowed to be used to publish applications within this namespace. Check the boxes next to the ingresses you want to allow and click **Allow selected**, or click **Disallow selected** to disallow their use in this namespace.

{% hint style="info" %}
This section is only visible when **Configure ingress controller availability per namespace** is enabled in the [Cluster Setup](/user/kubernetes/cluster/setup.md#networking-ingresses).
{% endhint %}

<figure><img src="/files/5EbmmaczQfRBmkjBTDzG" alt=""><figcaption></figcaption></figure>

### Registries

You can define the registries that are available within this namespace in this section. Select the registries from the **Select registries** dropdown to allow access.

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

### Storage

Use this section to enable quotas on your storage options for this namespace. To enable the use of quotas on a storage option, toggle **Enable quota** to on and set the **Maximum usage**. A Maximum usage value of `0` effectively prevents the usage of that storage option within the namespace.

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

### Summary

This section displays a summary of the actions that will be taken when clicking the Add namespace button.

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

When you're finished, click **Create namespace**.


---

# Agent Instructions: 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.portainer.io/user/kubernetes/namespaces/add.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.