# Management Zone with object inheritance in Kubernetes

**URL:** <https://community.dynatrace.com/t/management-zone-with-object-inheritance-in-kubernetes/36328>\
**Category:** Container platforms\
**Tags:** management-zones, kubernetes\
**Created:** [August 24, 2022, 2:52pm UTC](https://community.dynatrace.com/t/management-zone-with-object-inheritance-in-kubernetes/36328 "2022-08-24T14:52:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![a238574](https://avatars.discourse-cdn.com/v4/letter/a/edb3f5/32.png) [@a238574](https://community.dynatrace.com/u/a238574)\
**Post date:** [August 24, 2022, 2:52pm UTC](https://community.dynatrace.com/t/management-zone-with-object-inheritance-in-kubernetes/36328/1 "2022-08-24T14:52:46Z")

</div>

I am working with several Kubernetes clusters with 100’s of namespaces. I am trying to set up Management zones to break up the resources based on namespace names. With my initial tries I don’t seem to be inheriting the objects within the namespace in my management zone. I am hoping there is a simple solution

---

<div class="post-metadata">

**Author:** ![andre\_f](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/andre_f/32/29172_2.png) [@andre\_f](https://community.dynatrace.com/u/andre_f)\
**Post date:** [August 25, 2022, 7:45am UTC](https://community.dynatrace.com/t/management-zone-with-object-inheritance-in-kubernetes/36328/2 "2022-08-25T07:45:23Z")

</div>

Hi&nbsp;[@a238574](https://community.dynatrace.com/user/53959)

I’m not quite sure if this covers everything that is wanted, but with this you should see all workloads and pods in one namespace:

 ![andre_f_1-1661411738635.png](https://global.discourse-cdn.com/dynatrace/original/3X/7/1/712953377a6cd724d4e83eb635af9ac25288662c.png)

If something is missing you can write again what exactly should be included in the management zone.

---

<div class="post-metadata">

**Author:** ![andre\_f](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/andre_f/32/29172_2.png) [@andre\_f](https://community.dynatrace.com/u/andre_f)\
**Post date:** [August 25, 2022, 8:22am UTC](https://community.dynatrace.com/t/management-zone-with-object-inheritance-in-kubernetes/36328/3 "2022-08-25T08:22:28Z")

</div>

[@a238574](https://community.dynatrace.com/user/53959)&nbsp;In case the namespace itself, process groups and/or services should also be visible, these rules can be added.

For namespace:

 ![andre_f_0-1661415646646.png](https://global.discourse-cdn.com/dynatrace/original/3X/6/1/61e4adbd57e3ed739c9bdb8b2a1d1917c29a301d.png)

For process groups and services:

 ![andre_f_1-1661415709549.png](https://global.discourse-cdn.com/dynatrace/original/3X/3/2/32e3cf25988c3485ed562dea6baf9f4e3b3b246f.png)

---

<div class="post-metadata">

**Author:** ![Enrico\_F](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/enrico_f/32/23774_2.png) [@Enrico\_F](https://community.dynatrace.com/u/Enrico_F)\
**Post date:** [May 26, 2023, 3:35pm UTC](https://community.dynatrace.com/t/management-zone-with-object-inheritance-in-kubernetes/36328/4 "2023-05-26T15:35:06Z")

</div>

[@andre\_f](https://community.dynatrace.com/user/34598)&nbsp;I think your suggestion misses the point of this RFE which IMO is precisely about NOT having to create additional rules for any monitored entity types associated with a namespace, including workloads, containers, process groups, services and whatever else there can be.

Furthermore, there exists an optional Kubernetes component called [Hierarchical Namespace Controller](https://github.com/kubernetes-sigs/hierarchical-namespaces#the-hierarchical-namespace-controller-hnc)&nbsp;which can be installed for a cluster in order to structure namespaces hierarchically and can be really useful to manage huge numbers of namespaces. I think it would be nice if this could also be leveraged to structure management zones hierarchically across namespaces themselves…