Gracefully handle cloud resources name collisions

[fharper]

Which version of kubefirst are you using?

2.6.1

Which cloud provider?

Google Cloud

Which DNS?

None specific

Which installation type?

None specific

Which distributed Git provider?

None specific

Did you use a fork of gitops-template?

No

Which Operating System?

None specific

What is the issue?

When you try to create a cluster within a cloud that had some resources left using the same cluster name, the cloud Terraform step will fail without much more information. We should check if resources with the same name already exist and advice the user in the preflight checks or at a minimum fail gracefully. I think we check for cluster, but not all resources we need to create.

I only tested with Google Cloud, but I assume it's the same issue in any cloud.

Code of Conduct

• I agree to follow this project's Code of Conduct

[linear]

KON-41 Gracefully handle cloud resources name collisions

[fharper]

It's happening in all clouds, and it's a recurring issues our users have when they are testing Kubefirst.