From 7c50ec124bebfac2f5a02f605d3363f7fbda7e6c Mon Sep 17 00:00:00 2001 From: Laura Bailey Date: Tue, 6 Oct 2026 13:12:48 +1000 Subject: [PATCH] MBP-1173/ghissue-739 Broken links in Secure Agent Workspace pattern --- .../secure-agent-workspace/cluster-sizing.adoc | 3 ++- .../secure-agent-workspace/getting-started.adoc | 10 +++++----- .../secure-agent-workspace/troubleshooting.adoc | 4 ++-- 3 files changed, 9 insertions(+), 8 deletions(-) diff --git a/content/patterns/secure-agent-workspace/cluster-sizing.adoc b/content/patterns/secure-agent-workspace/cluster-sizing.adoc index ce5b6518c..75a0bf3b3 100644 --- a/content/patterns/secure-agent-workspace/cluster-sizing.adoc +++ b/content/patterns/secure-agent-workspace/cluster-sizing.adoc @@ -8,6 +8,7 @@ aliases: /secure-agent-workspace/cluster-sizing/ :imagesdir: /images :_content-type: ASSEMBLY include::modules/comm-attributes.adoc[] + include::modules/secure-agent-workspace/metadata-secure-agent-workspace.adoc[] [id="secure-agent-workspace-bare-metal"] @@ -65,4 +66,4 @@ The cluster needs a default storage class for the VM disks (`ReadWriteOnce`, 40 [id="secure-agent-workspace-model-serving"] == Model serving -By default, the agents use NVIDIA Nemotron on build.nvidia.com and need no GPU in the cluster. If you serve models on the cluster instead, for example with vLLM, add the GPU nodes that the model server needs. For more information, see link:ideas-for-customization[Ideas for customization]. +By default, the agents use NVIDIA Nemotron on build.nvidia.com and need no GPU in the cluster. If you serve models on the cluster instead, for example with vLLM, add the GPU nodes that the model server needs. For more information, see link:../ideas-for-customization/[Ideas for customization]. diff --git a/content/patterns/secure-agent-workspace/getting-started.adoc b/content/patterns/secure-agent-workspace/getting-started.adoc index a56876887..72f5c50eb 100644 --- a/content/patterns/secure-agent-workspace/getting-started.adoc +++ b/content/patterns/secure-agent-workspace/getting-started.adoc @@ -17,11 +17,11 @@ include::modules/comm-attributes.adoc[] * An {ocp} cluster with *bare-metal worker nodes* to provide hardware virtualization to run a separate {VirtProductName} VM for each workspace. {VirtProductName} does not support nested virtualization. ** *For on-premises deployments*, install {ocp} on bare-metal servers with Intel VT-x or AMD-V enabled in the firmware. ** *For public cloud deployments*, select bare-metal instance types for workers, for example, on AWS, select `m5.metal` or `c5n.metal`. -** See link:cluster-sizing[Cluster sizing] for advice on the size and number of nodes required. +** See link:../cluster-sizing/[Cluster sizing] for advice on the size and number of nodes required. ** You can create an {ocp} cluster by using the link:https://console.redhat.com/openshift/create[Red{nbsp}Hat Hybrid Cloud Console]. * A default storage class that can provision `ReadWriteOnce` volumes for the VM disks. * Cluster administrator access. End users need no {ocp} access: they sign in to the workspaces with Keycloak. -* An API key for each service that the default profile uses: build.nvidia.com (NVIDIA Nemotron) and Brave Search. To use a model server of your own instead, see link:ideas-for-customization[Ideas for customization]. +* An API key for each service that the default profile uses: build.nvidia.com (NVIDIA Nemotron) and Brave Search. To use a model server of your own instead, see link:../ideas-for-customization/[Ideas for customization]. * The `oc` CLI. For instructions, see link:https://docs.openshift.com/container-platform/latest/cli_reference/openshift_cli/getting-started-cli.html[Getting started with the OpenShift CLI]. * The Helm binary. For instructions, see link:https://helm.sh/docs/intro/install/[Installing Helm]. * The `openshell` CLI, version 0.1.x, from the link:https://github.com/NVIDIA/OpenShell/releases[OpenShell releases]. A 0.0.x CLI cannot connect to the 0.1.x gateway that this pattern installs. @@ -270,6 +270,6 @@ $ openshell --gateway alice --workspace default \ [id="next-steps-getting-started-saw"] == Next steps -* link:ideas-for-customization[Ideas for customization] -* link:cluster-sizing[Cluster sizing] -* link:troubleshooting[Troubleshooting] +* link:../ideas-for-customization/[Ideas for customization] +* link:../cluster-sizing/[Cluster sizing] +* link:../troubleshooting/[Troubleshooting] diff --git a/content/patterns/secure-agent-workspace/troubleshooting.adoc b/content/patterns/secure-agent-workspace/troubleshooting.adoc index 2afd8e40f..646a63c1c 100644 --- a/content/patterns/secure-agent-workspace/troubleshooting.adoc +++ b/content/patterns/secure-agent-workspace/troubleshooting.adoc @@ -31,7 +31,7 @@ Add bare-metal worker nodes (on public clouds, `*.metal` instance types) and che $ oc get nodes -l kubevirt.io/schedulable=true ---- + -For more information, see link:cluster-sizing[Cluster sizing]. +For more information, see link:../cluster-sizing/[Cluster sizing]. [id="troubleshooting-installer-saw"] === The installer in the VM fails @@ -116,7 +116,7 @@ Cause:: Sandboxes can reach only the hosts that their attached providers' profiles list, and only from the programs that the profiles list. Resolution:: -Check that the provider is attached to the sandbox (`openshell sandbox provider list `). Check also that its profile lists the host and port and the real path of the program that connects, such as `/usr/bin/node-*` for OpenClaw. For a custom model endpoint, the `openai` profile must name the endpoint's host. See link:ideas-for-customization[Ideas for customization]. +Check that the provider is attached to the sandbox (`openshell sandbox provider list `). Check also that its profile lists the host and port and the real path of the program that connects, such as `/usr/bin/node-*` for OpenClaw. For a custom model endpoint, the `openai` profile must name the endpoint's host. See link:../ideas-for-customization/[Ideas for customization]. [id="troubleshooting-cli-version-saw"] === The openshell CLI reports a version mismatch