Update JobSuccessPolicy documentations for the beta graduation

[tenzen-y]

This PR update is just the feature gate stage since there are no user-facing changes in the beta stage.

Part of: kubernetes/enhancements#3998

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name	Link
🔨 Latest commit	f6be581
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/66a24fa2a74308000889d04f

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	f6be581
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/66a24fa2d563720008738c9c
😎 Deploy Preview	https://deploy-preview-46970--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Princesso]

Hello @tenzen-y 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday July 16th 2024 18:00 PST. Thank you!

[carlory]

/hold
until kubernetes/kubernetes#126017 is merged.

[Shubham82]

FYI: The following upstream PR is closed kubernetes/kubernetes#126017, Instead of that kubernetes/kubernetes#126064 is opened for the same, but there is some talk to merge several PRs into one for this enhancement, Here is the comment for it: kubernetes/kubernetes#126064 (comment)
Wait until all corresponding PRs are merged.

[Princesso]

FYI: The following upstream PR is closed kubernetes/kubernetes#126017, Instead of that kubernetes/kubernetes#126064 is opened for the same, but there is some talk to merge several PRs into one for this enhancement, Here is the comment for it: kubernetes/kubernetes#126064 (comment) Wait until all corresponding PRs are merged.

Hello @Shubham82, I noticed that all the aforementioned upstream PRs are closed. Not of them got merged. Could you kindly let us know if other PRs were opened instead?

[Shubham82]

Hello @Shubham82, I noticed that all the aforementioned upstream PRs are closed. Not of them got merged. Could you kindly let us know if other PRs were opened instead?

Hi @Princesso, Here is the corresponding PR(combining all PRs into one), and it is merged now:
kubernetes/kubernetes#126067

[Shubham82]

removing the hold label, as the corresponding Upstream PR is merged.
/unhold

[Shubham82]

Thanks @tenzen-y for the PR, The changes look good to me.

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 25a3e69e1cc1ac2913a20d9c3fcfbfc2096088ea

[hacktivist123]

Hello @tenzen-y 👋! I'm reaching out from the Docs team. Just checking in as we approach Docs Freeze on Tuesday July 30th 18:00 PDT. This documentation appears to still be under review. To meet the Docs Freeze, this PR must have a technical review as well as lgtm and approve labels applied, without any unaddressed comments or concerns from SIG Docs. The status of this enhancement is marked as at risk for docs freeze. Thank you!

[tenzen-y]

Hello @tenzen-y 👋! I'm reaching out from the Docs team. Just checking in as we approach Docs Freeze on Tuesday July 30th 18:00 PDT. This documentation appears to still be under review. To meet the Docs Freeze, this PR must have a technical review as well as lgtm and approve labels applied, without any unaddressed comments or concerns from SIG Docs. The status of this enhancement is marked as at risk for docs freeze. Thank you!

Thank you for reminding me!
/assign @atiratree @soltysh

[tenzen-y]

@atiratree I addressed your comments. PTAL, thanks.

[atiratree]

Thanks, lgtm from sig-apps pov.

[tengqm]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 49b1ee60dafafce4bb9357c2768646d18526df9d

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tengqm

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:

• content/en/docs/OWNERS [tengqm]

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