Skip to content
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

Adding clarification about SSH private key #249

Merged
merged 1 commit into from
Feb 21, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion running/maintenance.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Prerequisites
Before you can effective maintain a cluster, you'll want to verify that you have these things.

* **Credentials for the cloud account** that's being used to manage the cluster's resources.
* **SSH access to the cluster.** An administrator can arrange this by adding your GitHub username to the ``github_usernames:`` list within the cluster's ``credentials.yml`` file.
* **SSH access to the cluster.** You'll need to download the SSH private key used by your deconst instance and put it in `keys/{instance}.private.key` where `instance` is the name of your instance in your `credentials.yml`
* **A clone of the deconst/deploy repository** from `GitHub <https://github.com/deconst/deploy>`_. If you monitor more than one Deconst cluster, it's helpful to have a separate clone for each and name the clone's directory after the cluster rather than just calling them all "deploy."
* **A copy of the credentials.yml file** for the instance. Your ops team should arrange for an out-of-band mechanism to securely distribute this file and stay up to date. Put it in the root directory of your ``deconst/deploy`` clone.

Expand Down