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

FAQ about cloud Terraform failure #808

Open
1 task done
fharper opened this issue Oct 30, 2024 · 0 comments
Open
1 task done

FAQ about cloud Terraform failure #808

fharper opened this issue Oct 30, 2024 · 0 comments

Comments

@fharper
Copy link
Contributor

fharper commented Oct 30, 2024

What type of suggestions?

Missing Information

What page is concerned?

No response

What version of the docs?

No response

What is the issue?

CleanShot 2024-10-30 at 09 36 24

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant