Delete gcp-deployer and tf-deployer directories

[rsdcastro]

This issue tracks clusterctl being the primary and only bootstrapping mechanism, with all the functionality that is currently in gcp-deployer and tf-deployer.

Current set of directories is: gcp-deployer, tf-deployer, and vsphere-deployer.

[rsdcastro]

Can we have a list of what this entails?

@karan Karan - can you confirm that "clusterctl create" has everything we need to get rid of the tf-deployer, otherwise can you file bugs and list them here? Once done, please assign to @mkjelland for equivalent GCP audit.

[rsdcastro]

/assign @karan

[karan]

Primarily, bootstrapping is what we are waiting for - #157

Once that's done, we can deprecate the existing tools.

[rsdcastro]

@mkjelland Just to confirm: is #157 sufficient to delete gcp-deployer?

[mkjelland]

@rsdcastro Yes, once that issue is done the gcp-deployer can be deleted. Although deletion might get a little more painful in the short term, because that issue is only for cluster creation. Issue #20 will also need to be done so that people know how to delete their clusters.

[roberthbailey]

Renaming since we now have gcp-deployer, tf-deployer, and vsphere-deployer directories.

[karan]

Since clusterctl create cluster works for vsphere and gcp, we should be okay to delete *-deployer. We can do it tomorrow, after discussing in the community meeting.

[roberthbailey]

Sweet!

[spew]

/assign @karan

[karan]

Okay so we have decided to hold off on deleting gcp-deployer for a few more days until the existing integration test is migrated and cluster delete works (@spew is working on that). vsphere and tf deployers will be deleted in the meantime.

[karan]

/kind cleanup