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: content/learning-paths/servers-and-cloud-computing/circleci-gcp/create_resource_class.md
+18-16Lines changed: 18 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,36 +7,38 @@ layout: learningpathall
7
7
---
8
8
9
9
## Create a Resource Class for Self-Hosted Runner in CircleCI
10
-
This guide explains how to create a **Resource Class** in the **CircleCI Web Dashboard** for a **self-hosted runner**.
11
-
A Resource Class defines a unique identifier for your runner and links it to your CircleCI namespace, allowing CircleCI jobs to targetyour custom machine environment.
10
+
This section explains how to create a Resource Class in the CircleCI Web Dashboard for a self-hosted runner.
11
+
A Resource Class is a unique identifier that links your self-hosted runner to your CircleCI organization (namespace). It defines the “machine type” that CircleCI jobs can target, ensuring that only authorized jobs run on your managed infrastructure, in this case, your SUSE Linux Arm64 VM on Google Cloud C4A (Axion).
12
12
13
13
### Steps
14
14
15
-
1.**Go to the CircleCI Web Dashboard**
16
-
- From the left sidebar, navigate to **Self-Hosted Runners**.
17
-
- You’ll see a screen asking you to accept the **terms of use**.
18
-
-**Check the box** that says **“Yes, I agree to the terms”** to enable runners.
19
-
- Then click **Self-Hosted Runners** to continue setup.
15
+
1. Open the CircleCI Web Dashboard
16
+
- Login or Create a new account at [CircleCI](https://app.circleci.com/home)
17
+
- In the left-hand navigation panel, click Self-Hosted Runners.
18
+
- If this is your first time setting up runners, you’ll be prompted to accept the Terms of Use.
19
+
Check “Yes, I agree to the terms” to enable runner functionality for your organization.
20
+
- After accepting, click Self-Hosted Runners again to continue the setup process.
Click **Create Resource Class** on your CircleCI dashboard.
26
+
On your CircleCI Dashboard, click Create Resource Class.
26
27
27
-
**Fill in the following details:**
28
+
Fill in the following details:
28
29
29
-
-**Namespace:** Your CircleCI username or organization name (e.g., `circleci`)
30
-
-**Resource Class Name:** A clear, descriptive name for your runner (e.g., `arm64`)
31
-
- Click **Create Resource Class**.
30
+
*Namespace: Your CircleCI organization or username (e.g., circleci)
31
+
*Resource Class Name: A clear, descriptive identifier for your runner (e.g., arm64)
32
+
* Once complete, click Create Resource Class to generate it.
32
33
33
34

34
35
35
36

36
37
37
-
3.**Save and Copy the Token**
38
-
- Once created, CircleCI will generate a **Resource Class Token**.
39
-
- Copy this token and store it securely — you will need it to register your runner on the GCP VM.
38
+
3. Save and Copy the Token
39
+
40
+
After creating the resource class, CircleCI automatically generates a Resource Class Token, a secure authentication key used to register your runner. Copy this token immediately and store it in a secure location.
41
+
You’ll need this token in the next step to connect your SUSE Arm64 runner on the Google Cloud C4A (Axion) VM to CircleCI.
40
42
41
43

0 commit comments