-
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
vsphere generate-yaml usability changes, timeout for clusterctl #302
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 @jessicaochen |
The verbosity improvements are good. The removal of the copy to the home directory is not functional. The vsphere GetKubeConfig assumes a specific location for the ssh key to use (https://github.com/kubernetes-sigs/cluster-api/blob/master/cloud/vsphere/deployer.go#L60). We need the key to be at that location after generation is done. We can have sanity check that will not overwite an existing file (unless the overwrite flag is specified) but I think it is non functional to have the deployer break. |
/retest |
907b64d
to
98696ad
Compare
/retest |
/lgtm |
…rnetes-sigs#302) * vsphere generate-yaml usability changes * Change timeouts, copy ssh keys if they dontexist
Add better install instructions for envsubst
What this PR does / why we need it: Change provider config generation a little bit to not overwrite ssh key files in
~/.ssh
.Bump up timeout in clusterctl for various polls.