Skip to content

Commit 690810a

Browse files
Update CMX VM ssh public key instructions (#3606)
* Update CMX VM ssh public key instructions --------- Co-authored-by: Paige Calvert <[email protected]> Co-authored-by: Paige Calvert <[email protected]>
1 parent 1f98193 commit 690810a

File tree

1 file changed

+65
-27
lines changed

1 file changed

+65
-27
lines changed

docs/vendor/testing-vm-create.md

Lines changed: 65 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,14 @@ This topic describes how to use Replicated Compatibility Matrix to create and ma
44

55
## Set Up SSH Access
66

7-
In order to access VMs that you create with Compatibility Matrix, you need to set up SSH access. You can do this using your personal GitHub account or a GitHub service account used by your team.
7+
To access VMs that you create with Compatibility Matrix, you need to set up SSH access. You can do this using your GitHub account, a personal public/private key, or a service account or bot with shared access.
88

9-
For setting up SSH access to VMs that you create on your local machine, Replicated recommends that you use your personal GitHub account. For setting up SSH access for VMs created in CI/CD workflows used by your team, use a GitHub service account. For more information, see the sections below.
9+
### Use Your GitHub Account
1010

1111
:::note
1212
Your GitHub usernames and SSH keys are synced to a VM when it is first created. If you update your GitHub username or keys after creating a VM, you can manually sync by updating your [Account Settings](https://vendor.replicated.com/account-settings) in the Vendor Portal and clicking **Save**.
1313
:::
1414

15-
### Use Your GitHub Account
16-
1715
To set up and verify SSH access for Compatibility Matrix VMs using your personal GitHub account:
1816

1917
1. Log in to your GitHub account and add an SSH key if you do not have one already. For information about how to generate and add a new SSH key, see [Generate a new SSH key](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generati[…]w-ssh-key) and [Adding a new SSH key to your GitHub account](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) in the GitHub documentation.
@@ -34,43 +32,83 @@ To set up and verify SSH access for Compatibility Matrix VMs using your personal
3432
3533
1. On the **Account Settings > Account Information** page, for **GitHub username**, add your GitHub username.
3634
37-
1. On the command line, authenticate with the Replicated CLI using your Vendor Portal account:
35+
1. Verify that SSH access was set up successfully:
3836
39-
```bash
40-
replicated login
41-
```
42-
:::note
43-
To log out of an existing session, first run `replicated logout`.
44-
:::
37+
1. On the command line, authenticate with the Replicated CLI using your Vendor Portal account:
4538
46-
1. Run the following command to verify that your SSH setup is working:
39+
```bash
40+
replicated login
41+
```
42+
:::note
43+
To log out of an existing session, first run `replicated logout`.
44+
:::
4745
48-
```bash
49-
50-
```
51-
If successful, you will see a message similar to the following:
46+
1. Run the following command to verify that your SSH setup is working:
5247
53-
```
54-
Hi <username>! You have successfully authenticated, use [VM_ID]@replicatedvm.com to access your VM.
55-
```
48+
```bash
49+
50+
```
51+
If successful, you will see a message similar to the following:
52+
53+
```
54+
Hi <username>! You have successfully authenticated, use [VM_ID]@replicatedvm.com to access your VM.
55+
```
56+
57+
:::note
58+
If you see the prompt `Are you sure you want to continue connecting (yes/no/[fingerprint])?`, type `yes` and press Enter to continue. You might see this prompt if it is the first time you are authenticating with the public/private SSH key in your GitHub account.
59+
:::
5660
57-
:::note
58-
If you see the prompt `Are you sure you want to continue connecting (yes/no/[fingerprint])?`, type `yes` and press Enter to continue. You might see this prompt if it is the first time you are authenticating with the public/private SSH key in your GitHub account.
59-
:::
61+
### Use a Personal Public/Private Key
6062
61-
### Use a Service Account
63+
To set up and verify SSH access for Compatibility Matrix VMs using a personal public/private key pair:
6264
63-
To automate the creation of VMs in your CI/CD workflows, you can use the flag `--ssh-public-key` to provide the SSH public key for a GitHub service account. For example:
65+
1. If you do not already have a public and private key, generate a new public/private key pair.
66+
67+
1. Log in to the Vendor Portal and go to [**Compatibility Matrix Settings**](https://vendor.replicated.com/compatibility-matrix/settings).
68+
69+
1. On the **Compatibility Matrix Settings > SSH Public Keys** page, upload your public key.
70+
71+
1. Verify that SSH access was set up successfully:
72+
73+
1. On the command line, authenticate with the Replicated CLI using your Vendor Portal account:
74+
75+
```bash
76+
replicated login
77+
```
78+
:::note
79+
To log out of an existing session, first run `replicated logout`.
80+
:::
81+
82+
1. Run the following command to verify that your SSH setup is working:
83+
84+
```bash
85+
86+
```
87+
If successful, you will see a message similar to the following:
88+
89+
```
90+
Hi <username>! You have successfully authenticated, use [VM_ID]@replicatedvm.com to access your VM.
91+
```
92+
93+
:::note
94+
If you see the prompt `Are you sure you want to continue connecting (yes/no/[fingerprint])?`, type `yes` and press Enter to continue. You might see this prompt if it is the first time you are authenticating with the public/private SSH key in your GitHub account.
95+
:::
96+
97+
### Use a Service Account {#github-service-account}
98+
99+
If you are setting up SSH access for VMs created in CI/CD workflows used by your team, you can use the SSH key of a service account or bot with shared access.
100+
101+
To automate the creation of VMs in your CI/CD workflows, use the flag `--ssh-public-key` to provide the SSH public key. For example:
64102
65103
```bash
66104
replicated vm create --distribution ubuntu --version 24.04 --ssh-public-key ~/.ssh/id_rsa.pub
67105
```
68106
69-
Using multiple SSH public keys:
107+
Or, to use multiple SSH public keys:
70108
71109
```bash
72110
replicated vm create --distribution ubuntu --version 24.04 --ssh-public-key ~/.ssh/id_rsa.pub --ssh-public-key ~/.ssh/id_ed25519.pub
73-
```
111+
```
74112
75113
## Create VMs
76114
@@ -291,4 +329,4 @@ To set the network policy of a VM to `airgap`:
291329
```bash
292330
replicated network update NETWORK_ID --policy airgap
293331
```
294-
Where `NETWORK_ID` is the ID of the network from the output of the `vm ls` command.
332+
Where `NETWORK_ID` is the ID of the network from the output of the `vm ls` command.

0 commit comments

Comments
 (0)