Skip to content

chart, salt: Bump Fluent Bit chart to 0.58.3 and Fluent Bit image to … - #5164

Merged
bert-e merged 2 commits into
development/136.0from
feature/MK8S-346-bump-fluent-bit
Oct 21, 2026
Merged

bert-e merged 2 commits into
development/136.0from
feature/MK8S-346-bump-fluent-bit

Conversation

@riadelhajjaji-scality

@riadelhajjaji-scality riadelhajjaji-scality commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary:

  • Bump the Fluent Bit chart from 0.57.7 to 0.58.3, and Fluent Bit from 5.0.7 to 5.1.3.
  • The chart releases in between only update the Fluent Bit image

Upstream changes reviewed against our configuration:

  • Adaptive flushing (flush.adaptive, 5.1.0): 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 (Remove_Keys with several Loki outputs,
    tenant_id_key): we use 3 Loki outputs, but neither option
  • in_systemd journal namespace support: opt-in, our input does not
    set it
  • Security hardening of input handling and the HTTP server: we only
    use the HTTP server for metrics and health checks
  • filter_kubernetes metadata for internal logs: only applies to the
    fluentbit_logs input, which we do not use
  • The image keeps the same base (Debian 13, libsystemd 257)

Acceptance criteria:

  • The CI passes: installation, expansion, upgrade and downgrade t
  • Fluent Bit pods run 5.1.3 and are Ready on every node

Closes: #MK8S-346

@bert-e

bert-e commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Hello riadelhajjaji-scality,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval ⭐
/bypass_build_status Bypass the build and test status ⭐
/bypass_commit_size Bypass the check on the size of the changeset TBA ⭐
/bypass_incompatible_branch Bypass the check on the source branch prefix ⭐
/bypass_jira_check Bypass the Jira issue check ⭐
/bypass_peer_approval Bypass the pull request peers' approval ⭐
/bypass_leader_approval Bypass the pull request leaders' approval ⭐
/bypass_source_branch_lineage Bypass the cross-branch contamination check ⭐
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request.
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e

bert-e commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

Peer approvals must include at least 1 approval from the following list:

@riadelhajjaji-scality

Copy link
Copy Markdown
Contributor Author

/changie Enhanced Bump Fluent Bit chart to 0.58.3 and Fluent Bit image to 5.1.3

@bert-e

bert-e commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

Peer approvals must include at least 1 approval from the following list:

@riadelhajjaji-scality
riadelhajjaji-scality marked this pull request as ready for review October 15, 2026 07:01
@riadelhajjaji-scality
riadelhajjaji-scality requested a review from a team as a code owner October 15, 2026 07:02
@bert-e

bert-e commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

Peer approvals must include at least 1 approval from the following list:

@claude

claude Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

LGTM

Review by Claude Code

@ezekiel-alexrod ezekiel-alexrod left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding release links to the changelog message could be handy too

#5163 (comment)

Comment thread buildchain/buildchain/versions.py
@riadelhajjaji-scality
riadelhajjaji-scality force-pushed the feature/MK8S-346-bump-fluent-bit branch from 9dcfef9 to 2b72197 Compare October 15, 2026 12:53
@bert-e

bert-e commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

Branches have diverged

This pull request's source branch feature/MK8S-346-bump-fluent-bit has diverged from
development/136.0 by more than 50 commits.

To avoid any integration risks, please re-synchronize them using one of the
following solutions:

  • Merge origin/development/136.0 into feature/MK8S-346-bump-fluent-bit
  • Rebase feature/MK8S-346-bump-fluent-bit onto origin/development/136.0

Note: If you choose to rebase, you may have to ask me to rebuild
integration branches using the reset command.

@riadelhajjaji-scality riadelhajjaji-scality self-assigned this Oct 16, 2026
@riadelhajjaji-scality
riadelhajjaji-scality force-pushed the feature/MK8S-346-bump-fluent-bit branch from 2b72197 to 61928ed Compare October 16, 2026 08:02
@riadelhajjaji-scality
riadelhajjaji-scality requested review from a team as code owners October 16, 2026 08:02
@riadelhajjaji-scality
riadelhajjaji-scality requested review from TeddyAndrieux and eg-ayoub and removed request for a team October 16, 2026 08:02
@claude

claude Bot commented Oct 16, 2026

Copy link
Copy Markdown
Contributor
  • No changelog entry: there is no file under .changes/unreleased/ and no /changie comment, even though earlier bumps have one and the /etc/machine-id mount fixes a user-visible bug (host logs not reaching Loki)
    - Post a /changie comment with an Enhanced entry for the chart 0.58.3 / Fluent Bit 5.1.3 bump
    - Add a separate Fix entry saying host (systemd journal) logs reach Loki again

    Review by Claude Code

@riadelhajjaji-scality

Copy link
Copy Markdown
Contributor Author

/changie Enhanced Bump fluent-bit chart to 0.58.3 and Fluent Bit image to v5.1.3

Comment thread charts/fluent-bit.yaml Outdated
Comment thread charts/fluent-bit.yaml Outdated
riadelhajjaji-scality and others added 2 commits October 20, 2026 11:28
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
@riadelhajjaji-scality
riadelhajjaji-scality force-pushed the feature/MK8S-346-bump-fluent-bit branch from 0e7a799 to 068c83b Compare October 20, 2026 09:34
@bert-e

bert-e commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

Peer approvals must include at least 1 approval from the following list:

@github-actions

Copy link
Copy Markdown
Contributor

✅ Changelog check passed.

@claude

claude Bot commented Oct 20, 2026

Copy link
Copy Markdown
Contributor
  • PR description is out of date: it still lists mounting /etc/machine-id and expects host logs ({job="fluent-bit", unit!=""}) in Loki as an acceptance criterion, but that change is no longer in this diff
    - Remove the /etc/machine-id bullet and the host-logs criterion, or link the separate PR that now carries the fix

    Review by Claude Code

@riadelhajjaji-scality

Copy link
Copy Markdown
Contributor Author

/approve

@bert-e

bert-e commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/136.0

The following branches will NOT be impacted:

  • development/123.0
  • development/124.0
  • development/124.1
  • development/125.0
  • development/126.0
  • development/127.0
  • development/128.0
  • development/129.0
  • development/130.0
  • development/131.0
  • development/132.0
  • development/133.0
  • development/134.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e

bert-e commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/136.0

The following branches have NOT changed:

  • development/123.0
  • development/124.0
  • development/124.1
  • development/125.0
  • development/126.0
  • development/127.0
  • development/128.0
  • development/129.0
  • development/130.0
  • development/131.0
  • development/132.0
  • development/133.0
  • development/134.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

Please check the status of the associated issue MK8S-346.

Goodbye riadelhajjaji-scality.

@bert-e
bert-e merged commit 2f5926f into development/136.0 Oct 21, 2026
62 of 63 checks passed
@bert-e
bert-e deleted the feature/MK8S-346-bump-fluent-bit branch October 21, 2026 17:57
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.

4 participants