Skip to content

Commit b8358c3

Browse files
authored
Update create_resource_class.md
1 parent 2916ff2 commit b8358c3

1 file changed

Lines changed: 18 additions & 16 deletions

File tree

content/learning-paths/servers-and-cloud-computing/circleci-gcp/create_resource_class.md

Lines changed: 18 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -7,36 +7,38 @@ layout: learningpathall
77
---
88

99
## 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 target your 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).
1212

1313
### Steps
1414

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.
2021

2122
![Self-Hosted Runners alt-text#center](images/shrunner0.png "Figure 1: Self-Hosted Runners ")
2223

23-
2. **Create a New Resource Class**
24+
2. Create a New Resource Class
2425

25-
Click **Create Resource Class** on your CircleCI dashboard.
26+
On your CircleCI Dashboard, click Create Resource Class.
2627

27-
**Fill in the following details:**
28+
Fill in the following details:
2829

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.
3233

3334
![Self-Hosted Runners alt-text#center](images/shrunner1.png "Figure 2: Create Resource Class ")
3435

3536
![Self-Hosted Runners alt-text#center](images/shrunner2.png "Figure 3: Details Resource Class & Namespace")
3637

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.
4042

4143
![Self-Hosted Runners alt-text#center](images/shrunner3.png "Figure 4: Resource Class Token")
4244

0 commit comments

Comments
 (0)