Repository navigation
chart, salt: Bump Fluent Bit chart to 0.58.3 and Fluent Bit image to … - #5164
Conversation
Hello riadelhajjaji-scality,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
|
/changie Enhanced Bump Fluent Bit chart to 0.58.3 and Fluent Bit image to 5.1.3 |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
|
LGTM |
ezekiel-alexrod
left a comment
There was a problem hiding this comment.
Adding release links to the changelog message could be handy too
9dcfef9 to
2b72197
Compare
Branches have divergedThis pull request's source branch To avoid any integration risks, please re-synchronize them using one of the
Note: If you choose to rebase, you may have to ask me to rebuild |
2b72197 to
61928ed
Compare
|
Bump the Fluent Bit chart from 0.57.7 to 0.58.3, and Fluent Bit itself from v5.0.7 to v5.1.3. The chart releases between 0.57.7 and 0.58.3 only update the Fluent Bit image, the rendered Salt state only changes the image tag and the version labels. Fluent Bit v5.0.7 -> v5.1.3 is a minor release with bug and security fixes, the main changes are: - 5.0.8/5.0.9: in_tail crash and out-of-bounds read fixes, out_loki tenant_id_key handling fix - 5.1.0: adaptive flushing (`flush.adaptive`), FIPS mode, new metrics and node exporter collectors - 5.1.2: in_systemd journal namespace support, filter_kubernetes namespace exclude, out_loki Remove_Keys fix with several Loki outputs - 5.1.3: security hardening of input handling and the HTTP server, fix of chunk placement under storage backpressure No breaking change upstream. Changes that could impact MetalK8s: - adaptive flushing is disabled by default, we keep `Flush 1` - the metrics used by our alerts (`fluentbit_input_ingestion_paused`, `fluentbit_input_storage_overlimit`, `fluentbit_output_retries_failed_total`) are still exposed - out_loki fixes: we use 3 Loki outputs, but neither Remove_Keys nor Tenant_ID_Key - in_systemd namespace support: opt-in, our input does not set it - HTTP server hardening: we only use it for metrics and health checks - filter_kubernetes metadata for internal logs: only applies to the fluentbit_logs input, which we do not use The digest has been updated by pulling the image from the registry using: gcrane digest cr.fluentbit.io/fluent/fluent-bit:5.1.3 Ref: MK8S-346
…t/helm-charts/releases/tag/fluent-bit-0.58.3) and Fluent Bit image to [v5.1.3](https://github.com/fluent/fluent-bit/releases/tag/v5.1.3) Auto-generated-by: changie-add-changelog
0e7a799 to
068c83b
Compare
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
|
✅ Changelog check passed. |
|
|
/approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue MK8S-346. Goodbye riadelhajjaji-scality. |
Summary:
Upstream changes reviewed against our configuration:
flush.adaptive, 5.1.0): disabled by default, wekeep
Flush 1fluentbit_input_ingestion_paused,fluentbit_input_storage_overlimit,fluentbit_output_retries_failed_total) are still exposedRemove_Keyswith several Loki outputs,tenant_id_key): we use 3 Loki outputs, but neither optionset it
use the HTTP server for metrics and health checks
fluentbit_logsinput, which we do not useAcceptance criteria:
Closes: #MK8S-346