-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Delete vsphere-deployer, tf-deployer. Mark gcp-deployer deprecated. #284
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: karan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @spew |
Thanks for opening this PR @karan. My thoughts are we should have feature parity in clusterctl before doing this (i.e. delete doesn't work yet)? I see we are waiting for the community meeting so no response needed. |
Okay so we have decided to hold off on deleting gcp-deployer for a few more days until the existing integration test is migrated (@spew is working on that). This PR has been updated to delete only vsphere and tf deployers in the meantime. |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A nit and a high level question.
High level question:
- clusterctl does not have support for terraform. It supports vsphere and gce at the moment. If we delete tf-deployer, then there will be no deployment tool for tf. Who uses the terraform stuff and do they need the tf-deployer still?
@@ -70,7 +70,7 @@ You can find an example implementation for GCE [here](https://github.com/kuberne | |||
|
|||
##### GCE Implementation | |||
|
|||
For GCE, a [yaml file](https://github.com/kubernetes-sigs/cluster-api/blob/master/gcp-deployer/machine_setup_configs.yaml) holds the list of valid machine setup configs, | |||
For GCE, a [config map](https://github.com/kubernetes-sigs/cluster-api/blob/6aecf9c80a1ca29b45cb43ebfd50ac0d57eb7132/clusterctl/examples/google/provider-components.yaml.template#L118) holds the list of valid machine setup configs, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it intentional to lock to a specific revision instead of using master?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The template is changing a lot and line numbers move around quite a bit.
Afaik, no one uses tf-deployer. The agreement was to not delete the provider for now, and others are free to work on it (including integrating with clusterctl). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok. Seems reasonable.
lgtm (leaving backslash to your second reviewer)
@dims expressed interest in extending the tf deployer to work with openstack but afaik hasn't started yet. I think we are saying that at this point he should build support into clusterctl instead. |
That's fair @roberthbailey thanks! |
/lgtm |
/hold cancel |
What this PR does / why we need it: Deletes the now unnecessary deployer tools in favor of
clusterctl
. I've also updated documentation where needed.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):#230
Not merging until after the community meeting on June 6.
/hold