From e9311bb9286b166ca14d9f7c87027795dd87d366 Mon Sep 17 00:00:00 2001 From: Peter Matseykanets Date: Fri, 25 Jul 2025 15:04:29 -0400 Subject: [PATCH] Fix Kubeconfigs example workflows page --- docs/api/workflows/kubeconfigs.md | 3 +-- versioned_docs/version-2.12/api/workflows/kubeconfigs.md | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/api/workflows/kubeconfigs.md b/docs/api/workflows/kubeconfigs.md index e5e92a391a9..518080ed4c8 100644 --- a/docs/api/workflows/kubeconfigs.md +++ b/docs/api/workflows/kubeconfigs.md @@ -29,8 +29,7 @@ kubectl patch feature ext-kubeconfigs -p '{"spec":{"value":false}}' ## Creating a Kubeconfig -Admins can delete any Kubeconfig, while regular users can only delete their own. When a Kubeconfig is deleted, the kubeconfig tokens are also deleted. -E.g. using a service account `system:admin` will lead to the following error: +Only a **valid and active** Rancher user can create a Kubeconfig. E.g. trying to create a Kubeconfig using `system:admin` service account will lead to an error: ```bash kubectl create -o jsonpath='{.status.value}' -f -<