Skip to content
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

Upgrade to Fluent-bit 1.6.2 #91

Closed

Conversation

allamand
Copy link

Signed-off-by: Sébastien Allamand [email protected]

Issue #, if available: #90

Description of changes:

Upgrade to Fluent-bit 1.6.2 which provide several fixes see : https://fluentbit.io/announcements/v1.6.2/

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Signed-off-by: Sébastien Allamand <[email protected]>
@allamand allamand requested a review from a team as a code owner October 26, 2020 09:37
@PettitWesley PettitWesley changed the base branch from master to mainline October 30, 2020 00:14
@PettitWesley
Copy link
Contributor

So the reason why we haven't updated yet is because there is also this bug: #81

Which we are working on fixing and hoping to get out in the next Fluent Bit release (1.6.3) in a few days.

I am very open to feedback on this- do you think we should have created a release with 1.6.2 already, even though it has known bugs (though less bugs than 1.6.2), instead of waiting till we get everything fixed?

@allamand
Copy link
Author

allamand commented Nov 2, 2020

I think it a matter of time and benefits. If you say that it as already less bug, I woulad say it makes sense to publish new version already. In the meantime if it only matter of few day to wait for the correction this cal also makes sense.

For my side, i'm waiting for other corrections than this one, but there are lots of things i didn't see or measures the impacts, So I'll trust your choices :)

@PettitWesley
Copy link
Contributor

Superceded by #92 which will upgrade to 1.6.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants