diff --git a/README.md b/README.md
index 6e795ccac7..ea6ff19203 100644
--- a/README.md
+++ b/README.md
@@ -37,6 +37,9 @@ kubectl create -k "github.com/ray-project/kuberay/manifests/cluster-scope-resour
 kubectl apply -k "github.com/ray-project/kuberay/manifests/base?ref=v0.2.0"
 ```
 
+> Observe that we must use `kubectl create` to install cluster-scoped resources.
+> The corresponding `kubectl apply` command will not work. See [KubeRay issue #271](https://github.com/ray-project/kuberay/issues/271).
+
 #### Single Namespace version
 
 It is possible that the user can only access one single namespace while deploying KubeRay. To deploy KubeRay in a single namespace, the user
diff --git a/docs/deploy/installation.md b/docs/deploy/installation.md
index 7ce6648e17..5295acdf44 100644
--- a/docs/deploy/installation.md
+++ b/docs/deploy/installation.md
@@ -13,3 +13,6 @@ kubectl apply -k "github.com/ray-project/kuberay/manifests/base"
 kubectl create -k "github.com/ray-project/kuberay/manifests/cluster-scope-resources?ref=v0.2.0"
 kubectl apply -k "github.com/ray-project/kuberay/manifests/base?ref=v0.2.0"
 ```
+
+> Observe that we must use `kubectl create` to install cluster-scoped resources.
+> The corresponding `kubectl apply` command will not work. See [KubeRay issue #271](https://github.com/ray-project/kuberay/issues/271).