# Setting up Beats on a shared Cluster

**URL:** <https://discuss.elastic.co/t/setting-up-beats-on-a-shared-cluster/167392>\
**Category:** Beats\
**Created:** [February 7, 2019, 8:15am UTC](https://discuss.elastic.co/t/setting-up-beats-on-a-shared-cluster/167392 "2019-02-07T08:15:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andreas.maier](https://avatars.discourse-cdn.com/v4/letter/a/d78d45/32.png) [@andreas.maier](https://discuss.elastic.co/u/andreas.maier)\
**Post date:** [February 7, 2019, 8:15am UTC](https://discuss.elastic.co/t/setting-up-beats-on-a-shared-cluster/167392/1 "2019-02-07T08:15:21Z")

</div>

Hello everybody,

I have a more or less central openshift cluster I have to use for my applications. There are multiple other projects/namespaces on the cluster I have no access rights on and will also not get any rights there.

As we have a separate ELK stack (not in OpenShift) we are using due to performance and distribution reasons I am wondering how to integrate best in that scenario.

I would like to use Beats but I fear that I can not really use them because they are usually installed in kube-system and act as DaemonSet for all projects/namespaces. Is there a way to just have the Beats in my projects/namespaces also as a DaemonSet and filter out all messages that are from containers that are not within my project/namespace?

Thanks in advance and kind regads,  
Andreas

---

<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:** [March 7, 2019, 10:19am UTC](https://discuss.elastic.co/t/setting-up-beats-on-a-shared-cluster/167392/2 "2019-03-07T10:19:50Z")

</div>

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