You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When manually upgrading the fluent-bit version in the aws-for-fluent-bit image the new version of fluent-bit does not support Enable_Identity in the filters.
Describe alternatives you've considered
Getting AWS to do this themselves. However, they seem reluctant to upgrade to a supported fluent-bit version and prefer to maintain their not-a-fork of 1.9.10. aws/aws-for-fluent-bit#885
Additional context
One can either use AWS's fluent-bit with the other bugs etc associated with 1.9.10 and the "Enable_Identity" option. Or a new version of fluent-bit and not be able to use the entity id and helm charts supplied by AWS without modifying the values. (As described here). You'd obviously need to build your own image with the new version of the fluent-bit binary too, so modifying some values as yaml is a small extra leap.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When manually upgrading the fluent-bit version in the aws-for-fluent-bit image the new version of fluent-bit does not support Enable_Identity in the filters.
Describe the solution you'd like
Update and import the change found here to fluent-bit 1.9.10:
https://github.com/amazon-contributing/upstream-to-fluent-bit/pull/4/files
AWS seem to be keeping it to themselves and I don't see any PR for it.
Describe alternatives you've considered
Getting AWS to do this themselves. However, they seem reluctant to upgrade to a supported fluent-bit version and prefer to maintain their not-a-fork of 1.9.10. aws/aws-for-fluent-bit#885
Additional context
One can either use AWS's fluent-bit with the other bugs etc associated with 1.9.10 and the "Enable_Identity" option. Or a new version of fluent-bit and not be able to use the entity id and helm charts supplied by AWS without modifying the values. (As described here). You'd obviously need to build your own image with the new version of the fluent-bit binary too, so modifying some values as yaml is a small extra leap.
The text was updated successfully, but these errors were encountered: