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

Automated backport of #1539: Prevent parallel cleanup of kind clusters #1565

Conversation

skitt
Copy link
Member

@skitt skitt commented Feb 19, 2024

Backport of #1539 on release-0.16.

#1539: Prevent parallel cleanup of kind clusters

For details on the backport process, see the backport requests page.

@submariner-bot
Copy link

🤖 Created branch: z_pr1565/skitt/automated-backport-of-#1539-origin-release-0.16

@tpantelis tpantelis enabled auto-merge (rebase) February 27, 2024 15:43
@tpantelis tpantelis force-pushed the automated-backport-of-#1539-origin-release-0.16 branch 2 times, most recently from 585958f to a700c9a Compare February 27, 2024 19:27
skitt and others added 2 commits February 27, 2024 14:42
kind uses a lock file to protect kubeconfig when it updates it after
stopping a cluster, but it fails if the lock file already exists.
Avoid this by cleaning up serially.

Signed-off-by: Stephen Kitt <[email protected]>
...to fix CVE.

Signed-off-by: Tom Pantelis <[email protected]>
@tpantelis tpantelis force-pushed the automated-backport-of-#1539-origin-release-0.16 branch from a700c9a to 999053c Compare February 27, 2024 19:44
@tpantelis tpantelis merged commit 997a379 into submariner-io:release-0.16 Feb 27, 2024
44 checks passed
@submariner-bot
Copy link

🤖 Closed branches: [z_pr1565/skitt/automated-backport-of-#1539-origin-release-0.16]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants