From e27cfe6e6ab18e7834c10fad70ca08616de344dd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E9=87=8E=E6=BC=AB=E6=A8=AA=E6=B1=9F?=
 <58300575+class-undefined@users.noreply.github.com>
Date: Sun, 25 Jun 2023 23:12:10 +0800
Subject: [PATCH] docs: fix incorrect command in project documentation (#8191)

---
 docs/platforms/kubernetes/additional-clusters.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/platforms/kubernetes/additional-clusters.md b/docs/platforms/kubernetes/additional-clusters.md
index 2ae0d5c3db..3df1115a62 100644
--- a/docs/platforms/kubernetes/additional-clusters.md
+++ b/docs/platforms/kubernetes/additional-clusters.md
@@ -23,7 +23,7 @@ If you deployed Coder on Kubernetes, you can attach a kubeconfig as a secret.
 This assumes Coder is deployed on the `coder` namespace and your kubeconfig file is in ~/.kube/config.
 
 ```sh
-kubectl create secret generic kubeconfig-secret -n coder--from-file=~/.kube/config
+kubectl create secret generic kubeconfig-secret -n coder --from-file=~/.kube/config
 ```
 
 Modify your helm values to mount the secret: