OCPBUGS-81340: pacemaker CronJob: tune history limit and Job TTL

[jaypoulz]

Raise successfulJobsHistoryLimit to 12 and set ttlSecondsAfterFinished to 300s so finished Jobs are typically removed by the TTL-after-finished controller before the CronJob controller prunes for history, reducing SuccessfulDelete event spam on the CronJob (openshift-etcd).

This only helps alleviate the delete event spam, not the create event spam.

Made-with: Cursor

[openshift-ci-robot]

@jaypoulz: This pull request references Jira Issue OCPBUGS-81340, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Raise successfulJobsHistoryLimit to 12 and set ttlSecondsAfterFinished to 300s so finished Jobs are typically removed by the TTL-after-finished controller before the CronJob controller prunes for history, reducing SuccessfulDelete event spam on the CronJob (openshift-etcd).

This only helps alleviate the delete event spam, not the create event spam.

Made-with: Cursor

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 717b5d3c-f171-49ae-9bf8-359961edead4

📥 Commits

Reviewing files that changed from the base of the PR and between b37aef7 and 2361fb2.

📒 Files selected for processing (1)

• bindata/tnfdeployment/cronjob.yaml

---

Walkthrough

Updated a CronJob manifest: increased spec.successfulJobsHistoryLimit from 1 to 12, decreased spec.jobTemplate.spec.ttlSecondsAfterFinished from 600 to 300, and added an inline comment explaining how history limit and TTL interact for finished Job deletion and CronJob pruning. (≤50 words)

Changes

Cohort / File(s)	Summary
CronJob Configuration bindata/tnfdeployment/cronjob.yaml	Changed spec.successfulJobsHistoryLimit 1 → 12, changed spec.jobTemplate.spec.ttlSecondsAfterFinished 600 → 300, added inline comment clarifying the joint effect of history limit and TTL on finished Job deletion vs. CronJob pruning.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[eggfoobar]

/test e2e-aws-etcd-certrotation

[eggfoobar]

/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-techpreview

[openshift-ci]

@eggfoobar: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0d243f20-2c6e-11f1-9a34-23c49e266fdc-0

[eggfoobar]

/test e2e-aws-etcd-certrotation

[eggfoobar]

/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-techpreview

[openshift-ci]

@eggfoobar: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0ae31830-2caf-11f1-833c-3ccecba63957-0

[jaypoulz]

/jira refresh

[openshift-ci-robot]

@jaypoulz: This pull request references Jira Issue OCPBUGS-81340, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[jaypoulz]

/retest-required

[openshift-ci]

@jaypoulz: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-etcd-certrotation	b37aef7	link	false	/test e2e-aws-etcd-certrotation

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[jaypoulz]

/verified-by #1581 (comment) This job does not contain pathological events for job deletion. Job creation and completed will be handled by openshift/origin#30953

[jaypoulz]

/verified by #1581 (comment) This job does not contain pathological events for job deletion. Job creation and completed will be handled by openshift/origin#30953

[openshift-ci-robot]

@jaypoulz: This PR has been marked as verified by https://github.com/openshift/cluster-etcd-operator/pull/1581#issuecomment-4159550043 This job does not contain pathological events for job deletion. Job creation and completed will be handled by https://github.com/openshift/origin/pull/30953.

Details

In response to this:

/verified by #1581 (comment) This job does not contain pathological events for job deletion. Job creation and completed will be handled by openshift/origin#30953

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[fonta-rh]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fonta-rh, jaypoulz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• bindata/tnfdeployment/OWNERS [fonta-rh,jaypoulz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@jaypoulz: Jira Issue OCPBUGS-81340: Some pull requests linked via external trackers have merged:

• openshift/cluster-etcd-operator#1581

The following pull request, linked via external tracker, has not merged:

• openshift/origin#30953 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-81340 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

In response to this:

Raise successfulJobsHistoryLimit to 12 and set ttlSecondsAfterFinished to 300s so finished Jobs are typically removed by the TTL-after-finished controller before the CronJob controller prunes for history, reducing SuccessfulDelete event spam on the CronJob (openshift-etcd).

This only helps alleviate the delete event spam, not the create event spam.

Made-with: Cursor

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-robot]

Fix included in release 4.22.0-0.nightly-2026-04-10-145151