@danbroudy see https://github.com/jclouds/jclouds-labs-google/pull/118.
There is no generic call in jclouds to add SSH keys to instances. The way to configure that is by using the `TemplateOptions.authorizePublicKey(String key)` option when creating the nodes with the ComputeService. The current implementation already reads that property and configures the SSH key in the instance accordingly. So, with https://github.com/jclouds/jclouds-labs-google/pull/118, users will be able to access an instance by: * Not configuring credentials at all. jclouds will take care of creating a key pair so it can access the node to bootstrap it if needed. This default can be turned off by setting the `autoGenerateKeyPair` option to false in the template options. * Using the `authorizePublicKey` option in the template options to install their SSH key. They can provide also the `overrideLoginPrivateKey` option to configure the private key, if they don't want to delegate authentication to the ssh-agent. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/116#issuecomment-67940341
