Skip to content

FAQ about cloud Terraform failure #808

@fharper

Description

@fharper

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions