From e7e1619a0e9dd307a895f52b614dca1844209564 Mon Sep 17 00:00:00 2001 From: Ankita Ambar Date: Sun, 30 Aug 2026 21:30:14 +0530 Subject: [PATCH] docs: clarify ClusterWorkflowTemplate step is a direct kubectl operation (#4004) Signed-off-by: Ankita Ambar --- .../workflows/workflow-workload-configuration.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/platform-engineer-guide/workflows/workflow-workload-configuration.mdx b/docs/platform-engineer-guide/workflows/workflow-workload-configuration.mdx index 3a79c456..eaaaebf0 100644 --- a/docs/platform-engineer-guide/workflows/workflow-workload-configuration.mdx +++ b/docs/platform-engineer-guide/workflows/workflow-workload-configuration.mdx @@ -42,6 +42,12 @@ For managing secrets in production environments, refer to the [Secret Management ## Step 3: Update the ClusterWorkflowTemplate +`ClusterWorkflowTemplate` is an [Argo Workflows](https://argo-workflows.readthedocs.io/) resource, not an OpenChoreo abstraction — none of OpenChoreo's tooling (CLI, Backstage plugin, MCP) can create or update it, so this step is done directly with `kubectl` against the Workflow Plane cluster: + +```bash +kubectl edit clusterworkflowtemplate generate-workload +``` + The `generate-workload` ClusterWorkflowTemplate accepts OAuth and API server parameters as inputs. Update the default values to point to your identity provider and API server: ```yaml