-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewrite_tag not working as expected when we used Namespaced Custom Resource Definitions #1211
Comments
Hello @jkrbharath, can you provide more information? What is the release you use? How did you install it exactly via helm (cmd and/or values.yaml)? Thx! |
Hi @SvenThies |
Hey @jkrbharath, sry for the late reply. Can you please also share the Thx! |
I'm also experiencing this issue of rewrite tag for namespaced CRDs not working as expected. I have installed v3.1.0 via helm online. The rule |
@RadOctocode you have to use kubernetes filter I guess. |
Hi @cw-Guo , Could you please provide some working examples of namespaced CRDs? Thanks! |
Hi @jkrbharath , I think the main issue here is the filters you use to processs the kubernetes related fields. namespaced CR is just a practice how we can use fluent-bit, it relies on the So to be able to use it, you need the kubernetes filter to help you and avoid any processing over it in the cluster level. You can process it using namespaced CRs
|
We are using Helm for our deployment, we had no control over the rewrite tag. I would appreciate any reference example or documentation you can give me. |
Hi team, We have updated our filter configuration to only use the Kubernetes filter. Here is the current filter configuration:
Our output configuration is as follows:
Additionally, we have our fluentbit configuration on the namespace level:
Despite these configurations, we are still encountering the error "Created task=0x7f86a808f6a0 id=0 without routes, dropping." We are unsure about what we are missing. Your assistance in resolving this matter would be greatly appreciated. |
Describe the issue
I have been diligently following the documentation to establish Namespaced Custom Resource Definitions (CRDs) within our environment. However, during the setup process, I encountered an error message that reads:
"Created task=0x7f86a808f6a0 id=0 without routes, dropping."
This error suggests that Fluent Bit, the logging aggregator we're using, encountered a task without a defined route for processing. Despite following the setup instructions provided in the documentation, I'm uncertain about the root cause of this issue.
Context:
ClusterInput looks like
Fluentbit config for namespace app-1 looks like
output Crds looks like
config which is stored in secret named fluent-bit-config looks like
It got to do with rewrite_tag which is added after having namespaced crs.
it's probably not able to tell the dynamic matching works
Thanks
How did you install fluent operator?
Fluent Operator is deployed via Helm
Additional context
No response
The text was updated successfully, but these errors were encountered: