KEP-5440: graduate suspended Job features to GA

[Utkarshpandey0001]

What type of PR is this?

/kind feature
/sig apps
/hold

What this PR does / why we need it:

This prepares the Kubernetes core feature gate changes for KEP-5440 Stable graduation in v1.38.

It graduates both suspended Job mutation feature gates to GA:

• MutablePodResourcesForSuspendedJobs
• MutableSchedulingDirectivesForSuspendedJobs

Both gates remain enabled by default and are locked to their default values starting in v1.38. The generated feature-gate lifecycle references are updated accordingly.

The Job strategy and integration tests that intentionally exercise pre-GA disabled-gate behavior are pinned to older feature-gate emulation versions so the historical coverage remains valid after the gates are locked in v1.38.

Which issue(s) this PR is related to:

KEP: kubernetes/enhancements#5440

Special notes for your reviewer:

This PR is held until the KEP Stable update merges: kubernetes/enhancements#6307

Remaining items for the overall graduation:

• Stable KEP/PRR approval in kubernetes/enhancements
• Merge of the KEP Stable update
• Kubernetes documentation update in kubernetes/website
• Release-team/reviewer confirmation before the enhancement is treated as fully graduated

Local validation:

• go run test/compatibility_lifecycle/main.go feature-gates verify
• go run cmd/genfeaturegates/genfeaturegates.go -output=/private/tmp/k8s-feature-list.md
• diff -q test/compatibility_lifecycle/reference/feature_list.md /private/tmp/k8s-feature-list.md
• git diff --check

Notes:

• hack/update-featuregates.sh and hack/verify-featuregates.sh could not run directly on this machine because /bin/bash is 3.2 and the scripts require Bash >= 4.2. I ran the generator/verifier commands from those scripts directly instead.
• go test ./pkg/registry/batch/job did not complete locally because the build exhausted the available disk space before tests ran. I also retried a narrower no-vet run with go test -vet=off -p 1 -run 'TestJobStrategy_ValidateUpdate|TestJobStrategy_ValidateUpdate_MutablePodResources|TestJobStrategy_ValidateUpdate_MutableSchedulingDirectives' ./pkg/registry/batch/job, which failed for the same local no space left on device reason.
• Targeted test/integration/job tests were not run locally because the unit package compile already exhausted local disk space.

Does this PR introduce a user-facing change?

Graduated the `MutablePodResourcesForSuspendedJobs` and `MutableSchedulingDirectivesForSuspendedJobs` feature gates to GA. The gates are enabled and locked to their default value.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

KEP: https://github.com/kubernetes/enhancements/issues/5440

AI usage disclosure:

YES

AI was used to prepare the code change and PR text. The author is responsible for reviewing and validating all submitted changes; see AGENTS.md and CONTRIBUTING.md.

[kubernetes-prow]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[kubernetes-prow]

Welcome @Utkarshpandey0001!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[kubernetes-prow]

Hi @Utkarshpandey0001. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[Utkarshpandey0001]

/hold

Holding until kubernetes/enhancements#6307 merges.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Utkarshpandey0001
Once this PR has been reviewed and has the lgtm label, please assign janetkuo for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• pkg/features/OWNERS
• pkg/registry/batch/OWNERS
• test/compatibility_lifecycle/reference/OWNERS
• test/integration/job/OWNERS

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

[pacoxu]

/ok-to-test