Skip to content

tweak ft section of usage #34

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

Merged
merged 1 commit into from
Aug 12, 2024
Merged

tweak ft section of usage #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions USAGE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -349,8 +349,8 @@ that when the resources are recreated they will still have sufficient
quota to execute. The number of times an AppWrapper is reset is
tracked as part of its status; if the number of resets exceeds the
`RetryLimit`, then the AppWrapper moves into a `Failed` state and its
resources are deleted (thus finally releasing its quota). Deletion of
a top-level wrapped resource will cause the AppWrapper directly enter
resources are deleted (thus finally releasing its quota). External deletion
of a top-level wrapped resource will cause the AppWrapper to directly enter
the `Failed` state independent of the `RetryLimit`.

To support debugging `Failed` workloads, an annotation can be added to an
Expand Down