diff --git a/docs/reference-guides/rancher-manager-architecture/rancher-server-and-components.md b/docs/reference-guides/rancher-manager-architecture/rancher-server-and-components.md
index 7a588ac91b3..bb1cf170e7a 100644
--- a/docs/reference-guides/rancher-manager-architecture/rancher-server-and-components.md
+++ b/docs/reference-guides/rancher-manager-architecture/rancher-server-and-components.md
@@ -20,6 +20,16 @@ A high-availability Kubernetes installation is recommended for production.
 
 A Docker installation of Rancher is recommended only for development and testing purposes. The ability to migrate Rancher to a high-availability cluster depends on the Rancher version.
 
+To see deployed resources, run the following command:
+
+```bash
+kubectl get all -n <namespace>
+```
+If you have administrator privileges, you can also see these resources listed in the Rancher UI:
+
+1. Click **☰** and select a cluster.
+1. Select **More Resources** from the side navigation menu to view deployed resources by type.
+1. Select **Cluster** > **Projects/Namespaces** from the side navigation menu, then select a namespace,  to view deployed resources by namespace.
 The Rancher backup operator can be used to migrate Rancher from the single Docker container install to an installation on a high-availability Kubernetes cluster. For details, refer to the documentation on [migrating Rancher to a new cluster](../../how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md).
 
-The Rancher server, regardless of the installation method, should always run on nodes that are separate from the downstream user clusters that it manages. If Rancher is installed on a high-availability Kubernetes cluster, it should run on a separate cluster from the cluster(s) it manages.
\ No newline at end of file
+The Rancher server, regardless of the installation method, should always run on nodes that are separate from the downstream user clusters that it manages. If Rancher is installed on a high-availability Kubernetes cluster, it should run on a separate cluster from the cluster(s) it manages.