<p>Million dollar question - are you running your fluentD as a DaemonSet?  If not, there's a chance that fluentd simply isn't running on the node where some containers live.</p>
<p>Otherwise, my best guess is, it's missing permissions to read from all namespaces, especially since you mentioned you haven't attached a ServiceAccount to it.  If you used a public FluentD Helm chart such as <a href="https://github.com/fluent/helm-charts" rel="nofollow noreferrer">this one</a>, try making sure you're deploying it with rbac enabled, i.e.:</p>
<pre><code>rbac:
  create: true

serviceAccount:
  create: true
</code></pre>
<p>It'll also help if you post some logs from your fluentd container.</p>

CC BY-SA 4.0
2021-04-06T07:37:24.507Z
Yes. my issue was htat fluentd was not running on all nodes. My fluentd is running as a DameonSet.
Vini
CC BY-SA 4.0
2021-04-04T05:57:07.707Z
2021-04-04T05:57:07.707Z
maplebird
<p>I have a cluster installed on Openshift and used the Cluster Logging Operator and Elasticsearch Operator to enable logging on the cluster.</p>
<p>On Kibana, I am only able to see the logs from certain namespaces and not all the namespaces I have. How do I configure Fluentd to read logs from all pods in all namespaces?</p>
<p>I do not have a Fluentd service account (It was not created with the installation of the operator).</p>
<p>Also, the namespaces from which I don't see any logs have a node selector mentioned in them. Could that be a reason why the logs are not available?</p>

<openshift><kibana><fluentd>
Fluentd unable to read logs from all namespaces
Vini
# Fluentd unable to read logs from all namespaces

(Asked by: username_0 on 2021-03-26)

I have a cluster installed on Openshift and used the Cluster Logging Operator and Elasticsearch Operator to enable logging on the cluster.

On Kibana, I am only able to see the logs from certain namespaces and not all the namespaces I have. How do I configure Fluentd to read logs from all pods in all namespaces?

I do not have a Fluentd service account (It was not created with the installation of the operator).

Also, the namespaces from which I don't see any logs have a node selector mentioned in them. Could that be a reason why the logs are not available?

**Tags:** openshift, kibana, fluentd


---

## 1 answers

### Answer by username_1 on 2021-04-04. Score: 2 | Accepted answer

Million dollar question - are you running your fluentD as a DaemonSet?  If not, there's a chance that fluentd simply isn't running on the node where some containers live.
Otherwise, my best guess is, it's missing permissions to read from all namespaces, especially since you mentioned you haven't attached a ServiceAccount to it.  If you used a public FluentD Helm chart such as this one, try making sure you're deploying it with rbac enabled, i.e.:
rbac:
  create: true

serviceAccount:
  create: true

It'll also help if you post some logs from your fluentd container.

> **Comments:**
> **username_0**: Yes. my issue was htat fluentd was not running on all nodes. My fluentd is running as a DameonSet.  

---

