-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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] After deleting a cluster from the command line, creating a cluster with the same name from the command line will sometimes fail #7718
Comments
Hi @jwatte , by default, eksctl will delete the cluster's cloudformation stack asynchronously. Running the Could you also please check AWS Console and share the actual error? |
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. |
This issue was closed because it has been stalled for 5 days with no activity. |
What were you trying to accomplish?
Try to create a cluster from the command line with the same name as a previously deleted cluster.
What happened?
After this, I'm trying to re-create a cluster with the same name, but get the error:
How to reproduce it?
I create a cluster.
I wait for it to come up.
I apply nginx-ingress manifests to set up an ingress controller and a NLB.
I wait for that to come up.
I delete the cluster.
The cluster goes away, and eksctl says the cluster is deleted.
Anything else we need to know?
Bug #2014 reports this same problem, and documents a work-around that involves the web console.
However, the whole point of eksctl is to drive this process from the command line, suitable for automated processes.
Thus, the work-around is not a solution to the problem, and an open bug needs to exist to document this problem.
Possible solutions would be:
Versions
The text was updated successfully, but these errors were encountered: