You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add in the F.A.Q. something about the fact that usually, until this issue if fixed konstructio/kubefirst#2312, if the Terraform for cloud (step 8) failed, which mean no resources (or not all) has been created on the cloud of the user's choice, it's usually because of resources name collision. It means that when they deprovision or manually delete things, some resources left with the same cluster name. The solution is to start a new cluster installation by using a different name than previous ones which may have left over resources, or clean their cloud properly.
It's an issue that happens often as most people trying Kubefirst will use the same cluster name every time they do a new installation.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What type of suggestions?
Missing Information
What page is concerned?
No response
What version of the docs?
No response
What is the issue?
Add in the F.A.Q. something about the fact that usually, until this issue if fixed konstructio/kubefirst#2312, if the Terraform for cloud (step 8) failed, which mean no resources (or not all) has been created on the cloud of the user's choice, it's usually because of resources name collision. It means that when they deprovision or manually delete things, some resources left with the same cluster name. The solution is to start a new cluster installation by using a different name than previous ones which may have left over resources, or clean their cloud properly.
It's an issue that happens often as most people trying Kubefirst will use the same cluster name every time they do a new installation.
Code of Conduct
The text was updated successfully, but these errors were encountered: