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

[Bug] delete nodegroup requires --approve, but delete cluster doesn't - a surprise #7777

Open
consideRatio opened this issue May 22, 2024 · 5 comments
Labels
kind/bug priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases

Comments

@consideRatio
Copy link
Contributor

I ran eksctl delete cluster --config-file=... and expected a confirmation via --approve before it actually started working it as eksctl delete nodegroup does.

Versions

$ eksctl info

eksctl version: 0.177.0
kubectl version: v1.28.9
OS: linux
@thatsnotamuffin
Copy link

thatsnotamuffin commented May 24, 2024

Kind of a funny story. I just noticed this as well about 10 minutes ago and was coming here to submit a bug for this. So, I believe we definitely need a --approve flag for this similar to what is required for the delete nodegroup. I was expecting to get the output of the delete argument but instead it deleted the cluster. Thankfully, it was a cluster that needed deleting anyways.

Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Jun 24, 2024
@consideRatio
Copy link
Contributor Author

Removing stale

@github-actions github-actions bot removed the stale label Jun 25, 2024
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Jul 25, 2024
@consideRatio
Copy link
Contributor Author

Relevant

@TiberiuGC TiberiuGC added priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases and removed stale labels Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases
Projects
None yet
Development

No branches or pull requests

3 participants