From 0c1c799576c8c502747627a48003fbc62e6ca081 Mon Sep 17 00:00:00 2001 From: revital Date: Mon, 13 Oct 2025 13:53:09 +0300 Subject: [PATCH] Small edits --- docs/clearml_agent/clearml_agent_nvcr.md | 2 +- docs/clearml_agent/clearml_agent_string_template.md | 2 +- docs/clearml_agent/dynamic_edit_task_pod_template.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/clearml_agent/clearml_agent_nvcr.md b/docs/clearml_agent/clearml_agent_nvcr.md index 3bdafbdb..1125199d 100644 --- a/docs/clearml_agent/clearml_agent_nvcr.md +++ b/docs/clearml_agent/clearml_agent_nvcr.md @@ -4,7 +4,7 @@ title: NVCR Access To allow ClearML Agents to access NVIDIA's container registry (`nvcr.io`), the machine’s Docker infrastructure must first be configured with valid NGC credentials. This enables Agents to pull NVIDIA-provided containers, such as those used by the [NVIDIA NIM app](../webapp/applications/apps_nvidia_nim.md). The setup is -required once per worker node, not every time you run an app. +required once per worker node. Configure Docker access to the `nvcr` repository on [bare-metal/VM](#on-bare-metal--vm) or [Kubernetes](#on-kubernetes). diff --git a/docs/clearml_agent/clearml_agent_string_template.md b/docs/clearml_agent/clearml_agent_string_template.md index 75b7e99e..2bbbb1a5 100644 --- a/docs/clearml_agent/clearml_agent_string_template.md +++ b/docs/clearml_agent/clearml_agent_string_template.md @@ -13,7 +13,7 @@ For example, `"${CLEARML_TASK.project}"` will be replaced with the Task's projec ## Single-value Variables -These variable resolve to a single value. You can use them directly in a template, without specifying any path. +These variables resolve to a single value. You can use them directly in a template, without specifying any path. For example `"${CLEARML_QUEUE_NAME}"` will be replaced with the name of the queue from which the task was pulled. diff --git a/docs/clearml_agent/dynamic_edit_task_pod_template.md b/docs/clearml_agent/dynamic_edit_task_pod_template.md index c58977a7..af24069c 100644 --- a/docs/clearml_agent/dynamic_edit_task_pod_template.md +++ b/docs/clearml_agent/dynamic_edit_task_pod_template.md @@ -70,7 +70,7 @@ agentk8sglue: * When defining a custom code module, by default the agent will start watching pods in all namespaces across the cluster. If you do not intend to give a `ClusterRole` permission, make sure to set the - `CLEARML_K8S_GLUE_MONITOR_ALL_NAMESPACES` env to `"0"` to prevent the Agent to try listing pods in all namespaces. + `CLEARML_K8S_GLUE_MONITOR_ALL_NAMESPACES` env to `"0"` to prevent the Agent from trying to list pods in all namespaces. Instead, set it to `"1"` if namespace-related changes are needed in the code. ```yaml