Add note about resource quota

Relates to: harvester/harvester#5433

Signed-off-by: Volker Theile <[email protected]>

docs/rancher/resource-quota.md

@@ -20,21 +20,29 @@ description: ResourceQuota allows administrators to set resource limits per name
 In Harvester, ResourceQuota can define usage limits for the following resources:
 - **CPU:** Limits compute resource usage, including CPU cores and CPU time.
 - **Memory:** Limits the usage of memory resources in bytes or other recognizable memory units.
+- **Storage:** Limits the usage of storage resources.
 
 ## Set ResourceQuota via Rancher
 In the Rancher UI, administrators can configure resource quotas for namespaces through the following steps:
 
 1. Click the hamburger menu and choose the **Virtualization Management** tab.
 1. Choose one of the clusters and go to **Projects/Namespaces** > **Create Project**.
 1. Specify the desired project **Name**. Next, go to the **Resource Quotas** tab and select the **Add Resource** option. Within the **Resource Type** field, select either **CPU Limit** or **Memory Limit** and define the **Project Limit** and **Namespace Default Limit** values.
-  ![](/img/v1.2/rancher/create-project.png)
+  ![](/img/v1.4/rancher/create-project.png)
 
 You can configure the **Namespace** limits as follows: 
 
 1. Find the newly created project, and select **Create Namespace**.
 1. Specify the desired namespace **Name**, and adjust the limits.
 1. Complete the process by selecting **Create**.
-  ![](/img/v1.2/rancher/create-namespace.png)
+  ![](/img/v1.4/rancher/create-namespace.png)
+
+:::note
+Please note that the provisioning of VMs for guest clusters is rejected if 
+the resource quotas are reached. Rancher responds by retrying to create a
+new machine in a loop. This results in a temporary transient error in the
+cluster that is not recorded as the machine is deleted and recreated.
+:::
 
 ## Overhead memory of virtual machine
 Upon creating a virtual machine (VM), the VM controller seamlessly incorporates overhead resources into the VM's configuration. These additional resources intend to guarantee the consistent and uninterrupted functioning of the VM. It's important to note that configuring memory limits requires a higher memory reservation due to the inclusion of these overhead resources.