From 7e8c0428c6a339d00c74212ef0abb708c496777a Mon Sep 17 00:00:00 2001 From: adminturneddevops Date: Thu, 7 May 2026 12:09:10 -0400 Subject: [PATCH] object update Signed-off-by: adminturneddevops --- .../nemoclaw-kagent-sandbox-secure-production-imp.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/blogContent/nemoclaw-kagent-sandbox-secure-production-imp.mdx b/src/blogContent/nemoclaw-kagent-sandbox-secure-production-imp.mdx index ce9b49c..56691df 100644 --- a/src/blogContent/nemoclaw-kagent-sandbox-secure-production-imp.mdx +++ b/src/blogContent/nemoclaw-kagent-sandbox-secure-production-imp.mdx @@ -50,7 +50,7 @@ With the theory and the "why" talked about in the two previous sections, let's s ```yaml apiVersion: kagent.dev/v1alpha2 -kind: Sandbox +kind: AgentHarness metadata: name: my-sandbox namespace: kagent @@ -65,7 +65,7 @@ spec: 2. Run the following to see your sandbox on the terminal: ```shell -kubectl get sandboxes -n kagent +kubectl get agentharness -n kagent ``` 3. You can then use your sandbox within the kagent UI. @@ -110,7 +110,7 @@ kubectl -n kagent create secret generic telegram-credentials \ ```yaml apiVersion: kagent.dev/v1alpha2 - kind: Sandbox + kind: AgentHarness metadata: name: my-claw namespace: kagent