# What does "managed namespaces" mean exactly?

**URL:** <https://discuss.elastic.co/t/what-does-managed-namespaces-mean-exactly/334054>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [May 22, 2023, 11:25pm UTC](https://discuss.elastic.co/t/what-does-managed-namespaces-mean-exactly/334054 "2023-05-22T23:25:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nahh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nahh/32/83181_2.png) [@nahh](https://discuss.elastic.co/u/nahh)\
**Post date:** [May 22, 2023, 11:25pm UTC](https://discuss.elastic.co/t/what-does-managed-namespaces-mean-exactly/334054/1 "2023-05-22T23:25:04Z")

</div>

I'm looking in to installing ECK in my Kubernetes clusters and I'm stuck on one issue: in the helm chart for ECK we're asked to specify a list of "managed namespaces". What does that mean? Specifically, what is being managed and what are the ramifications of allowing (or disallowing) ECK to manage a namespace? I would like ECK to be able to get logs from pods found in any namespace but if I don't have to let it "manage" namespaces, that'd be great.

---

<div class="post-metadata">

**Author:** ![Thibault\_Richard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thibault_richard/32/50513_2.png) [@Thibault\_Richard](https://discuss.elastic.co/u/Thibault_Richard)\
**Post date:** [May 25, 2023, 8:44am UTC](https://discuss.elastic.co/t/what-does-managed-namespaces-mean-exactly/334054/2 "2023-05-25T08:44:11Z")

</div>

Hello,

> I would like ECK to be able to get logs from pods found in any namespace

I think this is more: I would like Filebeat managed by ECK to get logs from pods found in any namespace.

Managed namespaces are namespaces in which the ECK operator manages Elastic resources (Elasticsearch, Kibana, Beats, ...), defaults to all namespaces if empty or unspecified.

You should be able to configure ECK with a restricted list of managed namespaces and deploy Filebeat with RBAC which gives it access to all pods in your cluster.

---

<div class="post-metadata">

**Author:** ![nahh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nahh/32/83181_2.png) [@nahh](https://discuss.elastic.co/u/nahh)\
**Post date:** [May 25, 2023, 2:55pm UTC](https://discuss.elastic.co/t/what-does-managed-namespaces-mean-exactly/334054/3 "2023-05-25T14:55:59Z")

</div>

OK, thanks. The fact that the default is wide open is what gave me pause.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 22, 2023, 2:56pm UTC](https://discuss.elastic.co/t/what-does-managed-namespaces-mean-exactly/334054/4 "2023-06-22T14:56:00Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.