Skip to content
This repository was archived by the owner on Oct 22, 2024. It is now read-only.

Commit f44deb9

Browse files
authored
Merge pull request #1032 from DougTW/dm-eds-autotest
autotest.md: added trademark disclaimers
2 parents 22d8bb8 + 0e932aa commit f44deb9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/autotest.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,15 @@
44

55
Use the `make test` command.
66

7-
## QEMU and Kubernetes
7+
## QEMU and Kubernetes\*
88

99
E2E testing relies on a cluster running inside multiple QEMU virtual
1010
machines deployed by [GoVM](https://github.com/govm-project/govm). The
1111
same cluster can also be used interactively when real hardware is not
1212
available.
1313

1414
E2E testing is known to work on a Linux development host system. The user
15-
must be allowed to use Docker.
15+
must be allowed to use Docker\*.
1616

1717
KVM must be enabled. Usually this is the case when `/dev/kvm` exists.
1818
The current user does not need the privileges to use KVM and QEMU
@@ -23,7 +23,7 @@ Note that cloud providers often don't offer KVM support on their
2323
regular machines. Search for "nested virtualization" for your provider
2424
to determine whether and how it supports KVM.
2525

26-
Nested virtualization is also needed when using Kata Containers inside
26+
Nested virtualization is also needed when using Kata Containers\* inside
2727
the cluster. On Intel-based machines it can be enabled by loading the
2828
`kvm_intel` module with `nested=1` (see
2929
https://wiki.archlinux.org/index.php/KVM#Nested_virtualization). At
@@ -99,7 +99,7 @@ the default `pmem-govm` cluster name via the `CLUSTER` env variable.
9999
For example, this invocation sets up a cluster using an older release
100100
of Kubernetes:
101101

102-
```
102+
```
103103
TEST_KUBERNETES_VERSION=1.18 CLUSTER=kubernetes-1.18 make start
104104
```
105105

0 commit comments

Comments
 (0)