public/rancher-docs
1
0 Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-11-10 02:39:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1899 from pmatseykanets/fix-kubeconfigs-workflow-page

Browse Source 
Fix Kubeconfigs example workflows page
Original issue: #1631
This commit is contained in:
Peter Matseykanets authored and GitHub committed 2025-07-28 13:20:25 -04:00
2 parents 64ae1844a1 458ab31a00
commit c11e9cc617
2 files changed
+2 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/api/workflows/kubeconfigs.md
+1 -2
View File
@@ -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. For example, trying to create a Kubeconfig using a `system:admin` service account will lead to an error:
```bash
kubectl create -o jsonpath='{.status.value}' -f -<<EOF
versioned_docs/version-2.12/api/workflows/kubeconfigs.md
+1 -2
View File
@@ -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. For example, trying to create a Kubeconfig using a `system:admin` service account will lead to an error:
```bash
kubectl create -o jsonpath='{.status.value}' -f -<<EOF