# Namespaces and EKS

**URL:** <https://discuss.elastic.co/t/namespaces-and-eks/291904>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [December 15, 2021, 6:29am UTC](https://discuss.elastic.co/t/namespaces-and-eks/291904 "2021-12-15T06:29:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![George\_Leonard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/george_leonard/32/94100_2.png) [@George\_Leonard](https://discuss.elastic.co/u/George_Leonard)\
**Post date:** [December 15, 2021, 6:29am UTC](https://discuss.elastic.co/t/namespaces-and-eks/291904/1 "2021-12-15T06:29:03Z")

</div>

Hi all

So I see EKS creates a elastic-system namespace during the CRD creations.  
So question, would/should we deploy our own cluster bits into elastic-system ns...  
when you follow the quickstart they don't mention namespaces, implying your cluster ends in the default ns.  
so option #2, better is to rather push it into the elastic-system ns... but I'd rather think option #3 is better, push the cluster into say elastic-prod ns... thus allowing you for whatever reason, (maybe testing, or multi tenancy) to have a second cluster in say elastic-test ns.  
and thus leave the operator alone/in elastic-system,

Comment ?

G

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [December 15, 2021, 1:38pm UTC](https://discuss.elastic.co/t/namespaces-and-eks/291904/2 "2021-12-15T13:38:52Z")

</div>

The intention behind the `elastic-system` namespace is indeed to be reserved exclusively for the operator to isolate it from accidental deletion etc. Similar in spirit to how the Kubernetes control plane services are deployed in the `kube-system` namespace.

For your workloads (Elasticsearch clusters, Kibanas etc) you can chose whatever namespace you see fit which is why we do not include namespaces in our examples.

---

<div class="post-metadata">

**Author:** ![George\_Leonard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/george_leonard/32/94100_2.png) [@George\_Leonard](https://discuss.elastic.co/u/George_Leonard)\
**Post date:** [December 15, 2021, 1:54pm UTC](https://discuss.elastic.co/t/namespaces-and-eks/291904/3 "2021-12-15T13:54:17Z")

</div>

Hi Perbrc

Thanks for the confirmation, I would propose though, like allot of other technology/examples that do mention chose a namespace of your choice, to mention it, otherwise noobs will end deploying into default, until they've figured out it's a bad idea and then end redoing it, which is just not needed to start with.

Thanks

G

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [December 15, 2021, 2:30pm UTC](https://discuss.elastic.co/t/namespaces-and-eks/291904/4 "2021-12-15T14:30:20Z")

</div>

I raised an [issue](https://github.com/elastic/cloud-on-k8s/issues/5170) to highlight our intention behind the `elastic-system` namespace in the docs.

Deploying into the `default` namespace is fine if you are just starting to use ECK and are still in the process of evaluation and experimentation. For anything production grade I would assume that working with namespaces in Kubernetes will no longer be a issue, but we can look into adding a sentence to the docs.

---

<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:** [January 12, 2022, 2:31pm UTC](https://discuss.elastic.co/t/namespaces-and-eks/291904/5 "2022-01-12T14:31:17Z")

</div>

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