> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/frequently-asked-questions/how-to-implement-hierarchical-namespaces-in-pmk-cluster.md).

# How to Implement Hierarchical Namespaces in PMK Workload Cluster

## Problem

* How to apply comparable policies to many namespaces, such as granting access to team members.
* How to give some amount of resources to a team (similar to ResourceQuota), and it can distribute those resources between subnamespaces.
* How to provide team/group level access to create namespaces themselves as isolation units for their services.

## Environment

* Platform9 Managed Kubernetes - v5.6 or Higher

## Procedure

* Hierarchical Namespaces is a simple extension to Kubernetes namespaces that addresses some of the shortcomings of the namespace mentioned above.
* It addresses these problems by allowing one to organise their namespaces into trees, ability to create new namespaces within those trees and allowing to apply policies to those trees (or their subtrees).
* Something like below where each of these being namespaces -

{% tabs %}
{% tab title="Bash" %}

```bash
acme-org
└── team-a
     └── service-1
```

{% endtab %}
{% endtabs %}

* By doing this it is easy to manage groups of namespaces that share a common concept of ownership. They are especially useful in clusters that are shared by multiple teams, but the owners do not need to be people.

## Additional Information

{% hint style="info" %}
**Info**

Please refer to the below upstream documents regarding the same,

<https://kubernetes.io/blog/2020/08/14/introducing-hierarchical-namespaces/>

<https://github.com/kubernetes-sigs/hierarchical-namespaces/blob/master/docs/user-guide/concepts.md#basic-concepts>
{% endhint %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmk/frequently-asked-questions/how-to-implement-hierarchical-namespaces-in-pmk-cluster.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.