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: e7f2ca19-c752-41bc-bc88-d9117bb0113d

📥 Commits

Reviewing files that changed from the base of the PR and between 94594c8 and b37aef7.

📒 Files selected for processing (1)

• bindata/tnfdeployment/cronjob.yaml

---

Walkthrough

A CronJob configuration update that increases the successful job history limit from 1 to 12 and decreases the job TTL from 600 to 300 seconds, with an added explanatory comment clarifying the relationship between these retention parameters.

Changes

Cohort / File(s)	Summary
CronJob Configuration bindata/tnfdeployment/cronjob.yaml	Updated spec.successfulJobsHistoryLimit from 1 to 12, reduced spec.jobTemplate.spec.ttlSecondsAfterFinished from 600 to 300, and added inline comment documenting the interaction between TTL deletion and CronJob pruning mechanisms.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 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.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 [jaypoulz]

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

[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 tests 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
ci/prow/unit	b37aef7	link	true	/test unit
ci/prow/e2e-aws-ovn-single-node	b37aef7	link	true	/test e2e-aws-ovn-single-node

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.