Skip to content

Cj docs fix images on torque agent on suse rke2 page #526

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
qkalsky merged 3 commits into from
Oct 5, 2026
Merged

Cj docs fix images on torque agent on suse rke2 page #526

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
aeab61c
Fix the images that were rendering poorly and on the same line as tex…
Oct 5, 2026
27d978a
Fix spelling issue with CIS
Oct 5, 2026
74c3780
Remove CIS and RKE from the wordlist since we escape them with backticks
Oct 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions .wordlist.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -568,5 +568,4 @@ RHEL
OpenSearch
datetime
schemas
RKE
CIS
RKE
7 changes: 4 additions & 3 deletions docs/torque-agent/torque-agent-on-suse-rke2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,15 +30,16 @@ Torque agent can be installed on a [SUSE Rancher Kubernetes Engine 2 (RKE2)](htt
- To create resources on your cloud using Terraform, there is no built-in authentication between RKE2 and Torque. Store your cloud credentials in the Torque secret store and use them in your Terraform deployment.

:::tip
If your RKE2 cluster runs with the CIS hardening profile (`profile: cis`), Pod Security Admission is enforced cluster-wide. Make sure the namespaces used by the agent and by your environments allow the workloads Torque creates in them.
If your RKE2 cluster runs with the `CIS` hardening profile (`profile: cis`), Pod Security Admission is enforced cluster-wide. Make sure the namespaces used by the agent and by your environments allow the workloads Torque creates in them.
:::

## Setup

1. In Torque's **Administration** page, open the **Cloud Accounts** tab.
2. Click **Connect a Cloud**.
3. Under __Where do you want to install the Agent?__, select __RKE2__. The __Kubernetes__ technology is selected for the agent automatically. Give the agent a name.
<img src="/img/rke2-connect-agent.png" alt="RKE2 agent connected" width="50%" />

<img src="/img/rke2-connect-agent.png" alt="RKE2 agent connected" width="75%" />
4. Click __Next__.
5. Click __Generate__. Torque displays two commands.
6. On the RKE2 node, copy and run the first command. It adds the RKE2 `kubectl` binary to your `PATH` and points `KUBECONFIG` to the RKE2 kubeconfig file:
Expand All @@ -53,7 +54,7 @@ If your RKE2 cluster runs with the CIS hardening profile (`profile: cis`), Pod S
kubectl apply -f https://portal.qtorque.io/api/settings/executionhosts/deployment/k***roi/deployment.yaml
```
8. A __Connected!__ status is displayed in Torque, indicating that the agent was successfully installed and can communicate with Torque.
<img src="/img/rke2-install-step.png" alt="RKE2 agent connected" width="50%" />
<img src="/img/rke2-install-step.png" alt="RKE2 agent connected" width="75%" />
9. Click __Associate to Space__ to connect the host to a space, and provide the details you obtained in the prerequisites section.

## Troubleshooting
Expand Down
Loading