Remove instances of actuated "bare" label

This label is discouraged and will be removed in the future. Specify an exact amount of vCPU and RAM instead. Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
self-actuated · Mar 22, 2024 · 310ed35 · 310ed35
1 parent 9f7cafa
commit 310ed35
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 5 deletions.
diff --git a/docs/test-build.md b/docs/test-build.md
@@ -32,16 +32,16 @@ Note that if you're running on an Arm64 machine, instead of `runs-on: actuated`,
     jobs:
         specs:
             name: specs
-            # runs-on: actuated-arm64
-            runs-on: actuated
+            # runs-on: actuated-arm64-2cpu-8gb
+            runs-on: actuated-arm64-2cpu-8gb
             steps:
             - uses: actions/checkout@v1
             - name: Check specs
               run: |
                 ./specs.sh
     ```
 
-    Note that the `runs-on:` field says `actuated` and not `ubuntu-latest`. This is how the actuated control plane knows to send this job to your agent.
+    Note that the `runs-on:` field says `actuated-` and not `ubuntu-latest`. This is how the actuated control plane knows to send this job to your agent. There are no fixed sets of vCPU and RAM, you can make up your own combinations.
 
     Then add `specs.sh` to the root of the repository, and remember, that you must run `chmod +x specs.sh` afterwards to make it executable.
 

diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
@@ -75,10 +75,10 @@ We've created simple instructions on how to set up a registry mirror to cache im
 
 ## A job is running out of RAM or needs more cores
 
-If you suspect a job is running out of RAM or would benefit from more vCPU, you can increase the allocation by changing the `actuated` label, as follows:
+If you suspect a job is running out of RAM or would benefit from more vCPU, you can increase the allocation by changing the `runs-on` label, as follows:
 
 ```yaml
--runs-on: actuated
+-runs-on: actuated-8cpu-8gb
 +runs-on: actuated-8cpu-16gb
 ```
 
@@ -90,6 +90,8 @@ Bear in mind that if you set the RAM higher than the default, this may result in
 
 The maximum amount of vCPU that can be set for a single job is 32 vCPU, this is an implementation detail of Firecracker and may change in the future.
 
+To find out exactly how many resources are required, see our [blog post on right sizing with the vmmeter tool](https://actuated.dev/blog/right-sizing-vms-github-actions).
+
 ## Disk space is running out for a job
 
 The disk space allocated for jobs is 30GB by default, but this value can be increased. Contact the actuated team for instructions on how to do this.