Open tptignor opened 4 years ago
We will try and recreate this - thank you
Unfortunately, this kind of configuration error is not caught by fluentd config validation command. The reason is that fluentd generates the main config based on the defined behaviour of the plugin and the IDs involved.
Hi. We just discovered this operator and it's been very impressive so far. However, we did see a bug through the use of ID fields which I wanted to report. The first error occurred when using similar filter blocks in two different namespaces, each of the form:
After changing the IDs for one of the ConfigMaps, I found myself still facing this second error. This was caused by the universal output I had configured for the kube-system namespace.
Evidently while I had just specified the es-local ID in one ConfigMap, the reloader generated two fluentd config sections for it. Thus the second error (for what looks like the same bug.)
The effect of both errors is that the DaemonSet pods repeatedly crash until the config is fixed.