Skip to content
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

block deleting namespaces if the namespace contains a volume #13880

Merged
merged 1 commit into from
Jul 21, 2022

Conversation

tgross
Copy link
Member

@tgross tgross commented Jul 21, 2022

When we delete a namespace, we check to ensure that there are no non-terminal
jobs, which effectively covers evals, allocs, etc. CSI volumes are also
namespaced, so extend this check to cover CSI volumes.

We'll also need to add this check for Secure Variables, but this is in a separate
PR because it'll need to be backported.

When we delete a namespace, we check to ensure that there are no non-terminal
jobs, which effectively covers evals, allocs, etc. CSI volumes are also
namespaced, so extend this check to cover CSI volumes.
@tgross tgross force-pushed the b-delete-ns-block-by-csivolume branch from 4096820 to 934388b Compare July 21, 2022 17:50
@tgross tgross added backport/1.1.x backport to 1.1.x release line backport/1.2.x backport to 1.1.x release line backport/1.3.x backport to 1.3.x release line type/bug labels Jul 21, 2022
@tgross tgross added this to the 1.3.x milestone Jul 21, 2022
@tgross tgross marked this pull request as ready for review July 21, 2022 18:13
@tgross tgross requested review from shoenig and lgfa29 July 21, 2022 18:13
Copy link
Member

@shoenig shoenig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@tgross tgross merged commit 7c231fd into main Jul 21, 2022
@tgross tgross deleted the b-delete-ns-block-by-csivolume branch July 21, 2022 20:13
tgross added a commit that referenced this pull request Jul 21, 2022
When we delete a namespace, we check to ensure that there are no non-terminal
jobs, which effectively covers evals, allocs, etc. CSI volumes are also
namespaced, so extend this check to cover CSI volumes.
tgross added a commit that referenced this pull request Jul 21, 2022
When we delete a namespace, we check to ensure that there are no non-terminal
jobs, which effectively covers evals, allocs, etc. CSI volumes are also
namespaced, so extend this check to cover CSI volumes.
tgross pushed a commit that referenced this pull request Jul 21, 2022
…#13885)

When we delete a namespace, we check to ensure that there are no non-terminal
jobs, which effectively covers evals, allocs, etc. CSI volumes are also
namespaced, so extend this check to cover CSI volumes.
tgross added a commit that referenced this pull request Jul 21, 2022
…#13886)

When we delete a namespace, we check to ensure that there are no non-terminal
jobs, which effectively covers evals, allocs, etc. CSI volumes are also
namespaced, so extend this check to cover CSI volumes.

Co-authored-by: Tim Gross <[email protected]>
@tgross tgross modified the milestones: 1.3.x, 1.3.3 Aug 23, 2022
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport/1.1.x backport to 1.1.x release line backport/1.2.x backport to 1.1.x release line backport/1.3.x backport to 1.3.x release line theme/storage type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants