Skip to content

Bumps components - #2546

Merged
bert-e merged 17 commits into
development/2.16from
improvement/ZENKO-5370
Oct 8, 2026
Merged

bert-e merged 17 commits into
development/2.16from
improvement/ZENKO-5370

Conversation

@francoisferrand

Copy link
Copy Markdown
Contributor
  • Set the backlog metrics interval through the generic override
  • Bump cloudserver 9.5.0-preview.1
  • Bump vault 8.12.0-preview.1
  • Bump scuba 1.2.0-preview.1
  • Bump s3utils 1.20.0-preview.1
  • Bump redis 7.2.16
  • Bump redis_exporter 1.92.1
  • Bump fzf/kaf/stern dev tools
  • Bump busybox 1.38.0
  • Bump rclone 1.75.1
  • Bump haproxy 3.0.28
  • Bump backbeat 9.5.0-preview.4
  • Bump ZKOP-604

Issue: ZENKO-5370

delthas and others added 13 commits September 21, 2026 15:34
The generic backbeat.configurationOverrides map reaches backbeat as
environment variables, and 9.5 answers most of those names from an entrypoint
that rewrites conf/config.json in place. The operator mounts that directory
read only, so the container dies before it serves anything:
KAFKA_BACKLOG_METRICS_INTERVALS is one of the 57 names rewritten that way,
which is what failed this suite eight runs in a row.

9.6 deleted the entrypoint and reads those names from the configuration schema
itself (BB-808), where joi also coerces the value, so the interval arrives as
the number the schema declares rather than as a string. That the operator
passes them to a backbeat that cannot take them is ZKOP-605.

Issue: ZENKO-5359
backlogMetricsIntervalSeconds was a dedicated CR field, added by
zenko-operator#626 and reverted by #633 right after v1.8.16 in favour of the
generic backbeat.configurationOverrides map. The two spellings never coexist
in a released operator: v1.8.16 knows only the field, and every 1.8 release
after it knows only the override. So the e2e config and the operator pin have
to move together, and bumping the operator without this change breaks the
whole suite on a rejected field.

KAFKA_BACKLOG_METRICS_INTERVALS is backbeat's declared env alias for
kafka.backlogMetrics.intervalS, so the value reaches the same config key with
the same unit the removed field used -- as of 9.6, bumped just before this,
which is also the first release the map can be passed to at all. It is set on
the four consumers whose lag the lifecycle conductor waits on.

Issue: ZENKO-5359
@bert-e

bert-e commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Hello francoisferrand,

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 5, 2026

Copy link
Copy Markdown
Contributor

Incorrect fix version

The Fix Version/s in issue ZENKO-5370 contains:

  • None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 2.16.0

Please check the Fix Version/s of ZENKO-5370, or the target
branch of this pull request.

Comment thread solution/deps.yaml Outdated
@bert-e

bert-e commented Oct 5, 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

@francoisferrand

Copy link
Copy Markdown
Contributor Author

/approve

@scality scality deleted a comment from bert-e Oct 8, 2026
@scality scality deleted a comment from bert-e Oct 8, 2026
@bert-e

bert-e commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

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

  • ✔️ development/2.16

The following branches have NOT changed:

  • development/2.10
  • development/2.11
  • development/2.12
  • development/2.13
  • development/2.14
  • development/2.15
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

This pull request did not target the following hotfix branch(es) so they
were left untouched:

  • hotfix/2.13.5

Please check the status of the associated issue ZENKO-5370.

Goodbye francoisferrand.

The following options are set: approve

@bert-e
bert-e merged commit fdd7e77 into development/2.16 Oct 8, 2026
41 of 44 checks passed
@bert-e
bert-e deleted the improvement/ZENKO-5370 branch October 8, 2026 18:07
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.

5 participants