mirror of
https://github.com/etcd-io/etcd.git
synced 2024-09-27 06:25:44 +00:00
286bb0bace
This change switches over from 2x self-managed runners where side effects are possible between builds, to a pool of servers where each build runs in an isolated VM. The service is provided by actuated.dev, and sponsored by both Ampere and the CNCF. Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
18 lines
853 B
Markdown
18 lines
853 B
Markdown
# etcd arm64 test infrastructure
|
|
|
|
The infrastructure to build for arm64 is provided by [Equinix Metal](https://www.equinix.com/) via the [CNCF Community Infrastructure Lab](https://github.com/cncf/cluster/issues).
|
|
|
|
Previously, several maintainers were responsible for managing two bare-metal machines with a self-hosted runner installed. This was a manual process, and side effects could be left over from previous builds.
|
|
|
|
As part of a joint program between Ampere and the CNCF, [actuated.dev](https://actuated.dev) is providing managed Arm64 builds.
|
|
|
|
To use the new infrastructure, add the following to your workflow:
|
|
|
|
```yaml
|
|
runs-on: actuated-arm64-8cpu-32gb
|
|
```
|
|
|
|
The vCPUs and RAM are customizable, i.e. `actuated-arm64-8cpu-16gb` or `actuated-arm64-8cpu-32gb`.
|
|
|
|
For urgent support, contact @alexellis or the [actuated team](https://actuated.dev).
|