1.8.12: Track release and pendings -WIP-

[lecaros]

Core:

• ✔️ in_tail: enhance handling of high number of static files (#3947) #4590 (master & 1.8)
• ✔️ engine: fix grace period  #4355 related to [Windows 2016] Fluent Bit service enters a flush loop when trying to stop the service #4300 (merged for 1.8.11)
• ✔️ upstream: fix deadlock when destroying connections #4362 related to [Windows 2016] Fluent Bit service enters a flush loop when trying to stop the service #4300 (merged for 1.8.11)
• ✔️ upstream: async connection timeout coroutine resume fix #4140 related to [Windows 2016] Fluent Bit service enters a flush loop when trying to stop the service #4300, merged to master already. Merged 1.8.12: Track release and pendings -WIP- #4645 for 1.8
• ✔️ : tests: internal: timeout: added coroutine hang test case #4605. Merged to master. Waiting for PR 1.8: backport event timeout unit test #4659 for 1.8
• ✔️ config: added dns resolver selector  #4420 related to [Windows 2016] Fluent Bit service enters a flush loop when trying to stop the service #4300 (merged in master and 1.8)
• ✔️ upstream: add new option 'net.connect_timeout_log_error' (#4473) #4474 related to [Windows 2016] Fluent Bit service enters a flush loop when trying to stop the service #4300.
• ✔️ [1.8] network: prefer ipv4 DNS results option #4501 (merged)

Plugins:

• ✔️ plugins: in_exec: don't eat last character of plugin output #4655 (merged in 1.8)
• ✔️ : aws: fork mbedtls 2.25.0 base64 utility to avoid 2.26.0+ performance hit #4422 Upgrade mbedtls to 2.28. Includes Core and S3 plugin. Merged in 1.8 1.8: upgrade mbedtls to v2.28 #4661
• in_forward: add new option 'tag_prefix' (#4455) #4466 Already merged to 1.8. Need docs
• ✔️ 1.8: backport ra check #4517 #4663
• ✔️ 1.8: backport #4596 #4668
• ✔️ 1.8: backport #4672 #4675
• ✔️ 1.8: out_stackdriver: protect against undefined metadata (#4664) #4678

[nokute78]

Could you add #4517 ?
It has not been merged 1.8 branch yet and user requested #4517 (comment).

[edsiper]

@nokute78 done, waiting for CI

[nokute78]

@edsiper Thank you.

[nokute78]

By the way, how about using milestone to track issue/PR ?
There is already https://github.com/fluent/fluent-bit/milestone/12 for v1.8.12.

[edsiper]

good idea, @lecaros ^

[nokute78]

We can add issue/PR to milestone below menu or
https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/associating-milestones-with-issues-and-pull-requests

[lecaros]

Hi @nokute78. Yes, I'm already tagging those with milestone Fluent Bit v1.8.12. The same for the next 1.9 version.

[jerome-leanspace]

I'm writing here because it seems related but I can create a new issue if needed
I can already see the 1.8.12 version in docker and the 1.8 and (-debug) was updated and they seem to be quite different, 1.8-debug is much bigger and doesn't have busybox or was moved to another location

[patrick-stephens]

1.8.12 moves to Debian 11 (Bullseye).
Busybox has been removed as the debug images are just bullseye-slim ones so already have a shell (in fact sh and bash) and package manager. Is there a specific issue without it as we probably do need to resolve that so please raise and tag me?

[patrick-stephens]

@jerome-leanspace just to check - are you all ok with the removal of Busybox? I want to make sure I've not missed something or we need to add any other tooling back in.

[jerome-leanspace]

@patrick-stephens yes I'm fine with it, however the change is not documented in the release notes or on the website (https://docs.fluentbit.io/manual/installation/docker)

[patrick-stephens]

Yes, I thought I had raised a PR on docs but will fix that now.
The change notes should capture it in 1.9+ as the dockerfiles are all in the main repo now but for 1.8.12 this was a last minute backport via the deprecated repo so got missed.

[agup006]

With 1.8.12 shipped I believe we can close