Skip to content

Document the failure recovery mechanism #8069

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
kshalot wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Document the failure recovery mechanism #8069

kshalot wants to merge 4 commits into from

Conversation

@kshalot
Copy link
Contributor

@kshalot kshalot commented Dec 4, 2025 •
edited
Loading

What type of PR is this?

/kind documentation

What this PR does / why we need it:

The documentation was missing for this feature.

Which issue(s) this PR fixes:

Fixes #7872

Special notes for your reviewer:

I added the example reproduction of an issue and how it is being addressed by the controller so it's easier to conceptualize what this feature does, so it's easier for someone stumbling upon this page in the docs to know what "failure recovery" means in the context of Kueue right now.

Does this PR introduce a user-facing change?

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/documentation Categorizes issue or PR as related to documentation. labels Dec 4, 2025
@netlify
Copy link

netlify bot commented Dec 4, 2025 •
edited
Loading

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name Link
🔨 Latest commit 71bca10
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/6932aa9869b630000825e995
😎 Deploy Preview https://deploy-preview-8069--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Dec 4, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Dec 4, 2025

Hi @kshalot. Thanks for your PR.

I'm waiting for a github.com 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.

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.

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Dec 4, 2025
olekzabl
olekzabl approved these changes Dec 4, 2025
View reviewed changes
@mbobrovskyi
Copy link
Contributor

mbobrovskyi commented Dec 4, 2025

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 4, 2025
@kshalot kshalot force-pushed the docs/add-documentation-for-failure-recovery branch from b0c389a to b736e9a Compare December 4, 2025 14:42
olekzabl
olekzabl approved these changes Dec 4, 2025
View reviewed changes
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Dec 4, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

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

@mimowo mimowo mentioned this pull request Dec 8, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mbobrovskyi mbobrovskyi Awaiting requested review from mbobrovskyi

@tenzen-y tenzen-y Awaiting requested review from tenzen-y

1 more reviewer

@olekzabl olekzabl olekzabl approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Document the PodFailureRecovery mechanism

4 participants

@kshalot @k8s-ci-robot @mbobrovskyi @olekzabl