-
Notifications
You must be signed in to change notification settings - Fork 87
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
Add SSH keypair to GCP Machines #5
Comments
Is that the reason why |
@ialidzhikov @DockToFuture is this done? How does |
On GCP the ssh keys are not provided during VM creation, check https://stackoverflow.com/a/27536795 and https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys |
@petersutter, @xrstf you may want to know about this issue as part of GEP-15. |
I am currently working on something else. However, I will try to spend some time in the coming weeks to fix this one. |
Merge pull request gardener#5 from pingcap/remove-sa
…-controllermanager (gardener#5) * Provide correct --service-cluster-ip-range to kube-apiserver and kube-controllermanager Signed-off-by: Artiom Diomin <[email protected]> * Configure cloud routes if IPv4 overlay is enabled Signed-off-by: Artiom Diomin <[email protected]> --------- Signed-off-by: Artiom Diomin <[email protected]>
…-controllermanager (gardener#5) * Provide correct --service-cluster-ip-range to kube-apiserver and kube-controllermanager Signed-off-by: Artiom Diomin <[email protected]> * Configure cloud routes if IPv4 overlay is enabled Signed-off-by: Artiom Diomin <[email protected]> --------- Signed-off-by: Artiom Diomin <[email protected]>
SSH keypairs are attached to a machine during machine creation for all providers except GCP at the moment.
Note:
After investigation, it was identified that the fix is required in Gardener and not in MCM, hence creating the issue here for better tracking
Ref gardener/machine-controller-manager#192 for more details
The text was updated successfully, but these errors were encountered: