Skip to content

Set the backlog metrics interval through the generic override - #2535

Open
delthas wants to merge 1 commit into
development/2.16from
improvement/ZENKO-5359/backbeat-configuration-overrides
Open

delthas wants to merge 1 commit into
development/2.16from
improvement/ZENKO-5359/backbeat-configuration-overrides

Conversation

@delthas

@delthas delthas commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

backbeat.backlogMetricsIntervalSeconds is a dedicated CR field the operator no longer has: scality/zenko-operator#626 added it, scality/zenko-operator#633 reverted it right after v1.8.16 in favour of the generic backbeat.configurationOverrides map.

The two spellings never coexist in a released operator:

operator backlogMetricsIntervalSeconds backbeat.configurationOverrides
v1.8.16 works absent — the field exists only on ZenkoSpecSorbet
v1.8.17 removed works

So the config and the operator pin have to move together, and bumping the operator without this change fails the whole suite on a rejected field. Hence both in one commit.

KAFKA_BACKLOG_METRICS_INTERVALS is backbeat's declared env alias for kafka.backlogMetrics.intervalS (intervalS: joi.number().default(60).meta({ env: 'INTERVALS' })), so the value reaches the same key with the same unit — seconds — as the removed field did. It is set on the four consumers whose lag the lifecycle conductor waits on.

Split out of #2532, which carries the same change but is blocked on a zenko-operator 1.9 PR and so cannot land on this timeline.

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. It is set on the four consumers whose
lag the lifecycle conductor waits on.

Issue: ZENKO-5359
@bert-e

bert-e commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Hello delthas,

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.

@delthas
delthas requested review from a team, benzekrimaha and francoisferrand September 16, 2026 13:49
@scality scality deleted a comment from bert-e Sep 16, 2026
@bert-e

bert-e commented Sep 16, 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

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