You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/vendor/testing-vm-create.md
+42-19Lines changed: 42 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,5 @@
1
+
import Prerequisites from "../partials/cmx/_prerequisites.mdx"
2
+
1
3
# Create VMs (Beta)
2
4
3
5
This topic describes how to use Replicated Compatibility Matrix to create and manage ephemeral VMs, which allows greater flexibility in testing VM-based installs such as the [Replicated Embedded Cluster](https://docs.replicated.com/intro-replicated#embedded-cluster).
@@ -7,20 +9,27 @@ This topic describes how to use Replicated Compatibility Matrix to create and ma
7
9
Compatibility Matrix VMs provide isolated Linux environments for testing your applications. Unlike clusters, VMs give you full control over the operating system and allow you to test installation methods that require direct OS access.
8
10
9
11
**When to use VMs vs Clusters:**
10
-
***Use VMs** for testing Embedded Cluster installers, air-gap installations, or when you need full OS control
11
-
12
-
***Use Clusters** for testing Kubernetes-based deployments and Helm installations. For more information about creating and managing clusters, see [Create Clusters](/vendor/testing-how-to).
12
+
***Use VMs** for testing Embedded Cluster installers, air-gap installations, or when you need full OS control.
13
+
***Use Clusters** for testing Kubernetes-based deployments and Helm installations. See [Create Clusters](/vendor/testing-how-to).
13
14
14
15
## Prerequisites
15
16
16
17
Before you can use Compatibility Matrix VMs, you must complete the following prerequisites:
17
18
18
-
*[Configure your GitHub username in Replicated Vendor Portal](team-management-github-username#procedure)
19
+
<Prerequisites/>
20
+
21
+
* Existing accounts must accept the TOS for the trial on the [**Compatibility Matrix**](https://vendor.replicated.com/compatibility-matrix) page in the Replicated Vendor Portal.
22
+
23
+
24
+
Prerequisites for SSH access to VMs:
25
+
26
+
*[Configure your GitHub username or GitHub service account in Replicated Vendor Portal](team-management-github-username#procedure)
19
27
20
28
* Make sure you have added your SSH key in your GitHub account. For instructions, see [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.
21
29
22
30
:::note
23
-
GitHub usernames and SSH keys are synced every 24hrs. To immediately sync: → [Account Settings](https://vendor.replicated.com/account-settings) > click Save. Keys are synced to the VM at time of creation, so any updates after creation are ignored.
31
+
Troubleshooting
32
+
Your GitHub usernames and SSH keys are synced to the VM when you first create it. If you update your GitHub username or keys after VM creation, you can manually sync by going to [Account Settings](https://vendor.replicated.com/account-settings) > click "Save."
24
33
:::
25
34
26
35
## Set Up SSH Access
@@ -37,7 +46,19 @@ If successful, you will see:
37
46
You have successfully authenticated, use [VM_ID]@replicatedvm.com to access your VM.
38
47
```
39
48
40
-
If you do not see this message, your public/private key likely was not available.
49
+
If you do not see this message, check if your public/private key has been properly set up with GitHub.
0 commit comments