Automated cherry pick of #63650: Never clean backoff in job controller

[cblecker]

Cherry pick of #63650 on release-1.10.

#63650: Never clean backoff in job controller

[k8s-ci-robot]

@cblecker: All 'parent' PRs of a cherry-pick PR must have one of the "release-note" or "release-note-action-required" labels, or this PR must follow the standard/parent release note labeling requirement.

The following parent PRs have neither the "release-note" nor the "release-note-action-required" labels: #63650.

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/test-infra repository.

[k8s-ci-robot]

@cblecker: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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/test-infra repository.

[k8s-github-robot]

This PR is not for the master branch but does not have the cherrypick-approved label. Adding the do-not-merge/cherry-pick-not-approved label.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cblecker
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: janetkuo

Assign the PR to them by writing /assign @janetkuo in a comment when ready.

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

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/controller/job/OWNERS
• test/e2e/apps/OWNERS [cblecker]

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

[cblecker]

/sig apps
/milestone v1.10
/kind bug
/priority critical-urgent

[k8s-github-robot]

[MILESTONENOTIFIER] Milestone Pull Request Needs Approval

@MaciekPytel @cblecker @janetkuo @soltysh @kubernetes/sig-apps-misc

Action required: This pull request must have the status/approved-for-milestone label applied by a SIG maintainer.

Pull Request Labels

• sig/apps: Pull Request will be escalated to these SIGs if needed.
• priority/critical-urgent: Never automatically move pull request out of a release milestone; continually escalate to contributor and SIG through all available channels.
• kind/bug: Fixes a bug discovered during the current release.

Help

• Additional instructions
• Commands for setting labels

[k8s-ci-robot]

@cblecker: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-kubernetes-bazel-build	1d247c7	link	/test pull-kubernetes-bazel-build
pull-kubernetes-e2e-gce-device-plugin-gpu	1d247c7	link	/test pull-kubernetes-e2e-gce-device-plugin-gpu
pull-kubernetes-e2e-gce	1d247c7	link	/test pull-kubernetes-e2e-gce
pull-kubernetes-typecheck	1d247c7	link	/test pull-kubernetes-typecheck
pull-kubernetes-e2e-kops-aws	1d247c7	link	/test pull-kubernetes-e2e-kops-aws
pull-kubernetes-integration	1d247c7	link	/test pull-kubernetes-integration
pull-kubernetes-bazel-test	1d247c7	link	/test pull-kubernetes-bazel-test
pull-kubernetes-kubemark-e2e-gce-big	1d247c7	link	/test pull-kubernetes-kubemark-e2e-gce-big
pull-kubernetes-kubemark-e2e-gce	1d247c7	link	/test pull-kubernetes-kubemark-e2e-gce
pull-kubernetes-verify	1d247c7	link	/test pull-kubernetes-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.