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
feat(runner): Replace patch by install ICU package for ARM runners (#1624)
* Update arm-runner-patch.tpl
The runtimeconfig.json files seem to have changed on the latest Amazon Linux AMI.
When running the user data scripts, the patch of these files fails which causes initialization of the runner instance to fail.
* fix patch again
* install libicu60 instead of patching
* remove arm-patch
* Revert "remove arm-patch"
This reverts commit 639c46e.
* Add ARM64 documentation
* Remove arm-runner-patch.tpl and include in install-runner.sh
* add arm64, ephemeral and windows examples to github workflow
Copy file name to clipboardExpand all lines: README.md
+5-6
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ To be able to support a number of use-cases the module has quite a lot configura
93
93
94
94
#### ARM64 support via Graviton/Graviton2 instance-types
95
95
96
-
When using the default example or top-level module, specifying an `instance_type` that matches a Graviton/Graviton 2 (ARM64) architecture (e.g. a1, t4g or any 6th-gen `g` or `gd` type), the sub-modules will be automatically configured to provision with ARM64 AMIs and leverage GitHub's ARM64 action runner. See below for more details.
96
+
When using the default example or top-level module, specifying `instance_types` that match a Graviton/Graviton 2 (ARM64) architecture (e.g. a1, t4g or any 6th-gen `g` or `gd` type), you must also specify `runner_architecture = "arm64"` and the sub-modules will be automatically configured to provision with ARM64 AMIs and leverage GitHub's ARM64 action runner. See below for more details.
97
97
98
98
## Usages
99
99
@@ -184,8 +184,6 @@ module "github-runner" {
184
184
}
185
185
```
186
186
187
-
**ARM64** support: Specify an `a1`, `t4g` or `*6g*` (6th-gen Graviton2) instance type to stand up an ARM64 runner, otherwise the default is x86_64.
188
-
189
187
Run terraform by using the following commands
190
188
191
189
```bash
@@ -322,9 +320,10 @@ This module also allows you to run agents from a prebuilt AMI to gain faster sta
322
320
Examples are located in the [examples](./examples) directory. The following examples are provided:
323
321
324
322
-_[Default](examples/default/README.md)_: The default example of the module
323
+
-_[ARM64](examples/arm64/README.md)_: Example usage with ARM64 architecture
325
324
-_[Ubuntu](examples/ubuntu/README.md)_: Example usage of creating a runner using Ubuntu AMIs.
326
325
-_[Windows](examples/windows/README.md)_: Example usage of creating a runner using Windows as the OS.
327
-
-_[Ephemeral](examples/ephemeral/README.md): Example usages of ephemeral runners based on the default example.
326
+
-_[Ephemeral](examples/ephemeral/README.md)_: Example usages of ephemeral runners based on the default example.
328
327
-_[Prebuilt Images](examples/prebuilt/README.md)_: Example usages of deploying runners with a custom prebuilt image.
329
328
-_[Permissions boundary](examples/permissions-boundary/README.md)_: Example usages of permissions boundaries.
330
329
@@ -345,7 +344,7 @@ The following sub modules are optional and are provided as example or utility:
345
344
346
345
### ARM64 configuration for submodules
347
346
348
-
When using the top level module configure `runner_architecture = arm64` and insure the list of `instance_types` matches. When not using the top-level ensure the bot properties are set on the submodules.
347
+
When using the top level module configure `runner_architecture = "arm64"` and ensure the list of `instance_types` matches. When not using the top-level, ensure these properties are set on the submodules.
349
348
350
349
## Debugging
351
350
@@ -354,7 +353,7 @@ In case the setup does not work as intended follow the trace of events:
354
353
- In the GitHub App configuration, the Advanced page displays all webhook events that were sent.
355
354
- In AWS CloudWatch, every lambda has a log group. Look at the logs of the `webhook` and `scale-up` lambdas.
356
355
- In AWS SQS you can see messages available or in flight.
357
-
- Once an EC2 instance is running, you can connect to it in the EC2 user interface using Session Manager. Check the user data script using `cat /var/log/user-data.log`. By default several log files of the instances are streamed to AWS CloudWatch, look for a log group named `<environment>/runners`. In the log group you should see at least the log streams for the user data installation and runner agent.
356
+
- Once an EC2 instance is running, you can connect to it in the EC2 user interface using Session Manager (use `enable_ssm_on_runners = true`). Check the user data script using `cat /var/log/user-data.log`. By default several log files of the instances are streamed to AWS CloudWatch, look for a log group named `<environment>/runners`. In the log group you should see at least the log streams for the user data installation and runner agent.
358
357
- Registered instances should show up in the Settings - Actions page of the repository or organization (depending on the installation mode).
359
358
360
359
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
# Action runners deployment with ARM64 architecture
2
+
3
+
This module shows how to create GitHub action runners using AWS Graviton instances which have ARM64 architecture. Lambda release will be downloaded from GitHub.
4
+
5
+
## Usages
6
+
7
+
Steps for the full setup, such as creating a GitHub app can be found in the root module's [README](../../README.md). First download the Lambda releases from GitHub. Alternatively you can build the lambdas locally with Node or Docker, there is a simple build script in `<root>/.ci/build.sh`. In the `main.tf` you can simply remove the location of the lambda zip files, the default location will work in this case.
8
+
9
+
> Ensure you have set the version in `lambdas-download/main.tf` for running the example. The version needs to be set to a GitHub release version, see https://github.com/philips-labs/terraform-aws-github-runner/releases
10
+
11
+
```bash
12
+
cd lambdas-download
13
+
terraform init
14
+
terraform apply
15
+
cd ..
16
+
```
17
+
18
+
Before running Terraform, ensure the GitHub app is configured. See the [configuration details](../../README.md#usages) for more details.
19
+
20
+
```bash
21
+
terraform init
22
+
terraform apply
23
+
```
24
+
25
+
You can receive the webhook details by running:
26
+
27
+
```bash
28
+
terraform output -raw webhook_secret
29
+
```
30
+
31
+
Be-aware some shells will print some end of line character `%`.
0 commit comments