-
Notifications
You must be signed in to change notification settings - Fork 91
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.
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
Metal3Data deletable while in-use #1356
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue is ready to be actively worked on.
Comments
metal3-io-bot
added
kind/bug
Categorizes issue or PR as related to a bug.
needs-triage
Indicates an issue lacks a `triage/foo` label and requires one.
labels
Dec 12, 2023
/triage accepted |
metal3-io-bot
added
triage/accepted
Indicates an issue is ready to be actively worked on.
and removed
needs-triage
Indicates an issue lacks a `triage/foo` label and requires one.
labels
Dec 12, 2023
Rozzii
added
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
and removed
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
labels
Dec 17, 2023
/assign |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
metal3-io-bot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
May 19, 2024
/remove-lifecycle stale |
metal3-io-bot
removed
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
May 20, 2024
/assign |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue is ready to be actively worked on.
What steps did you take and what happened:
What did you expect to happen:
The objects should be protected from deletion while in use, i.e. even when deletion is triggered they should have finalizers that their controllers do not remove if they are still in-use.
Environment:
kubectl version
): v1.28.3/kind bug
The text was updated successfully, but these errors were encountered: