diff --git a/infrastructure/longhorn/README.md b/infrastructure/longhorn/README.md
index 1dd981728637cf79248e2a6c2cda81fad1a4ad66..fa0dba370bbcb08b080f6674c5acb9b76e409d81 100644
--- a/infrastructure/longhorn/README.md
+++ b/infrastructure/longhorn/README.md
@@ -3,6 +3,14 @@ Longhorn
 
 This component is deployed to provide persistent storage replicated across the nodes in an easy fashion.
 
+Nice to knows
+---
+
+- [volume-expansion is offline expansion only.](https://github.com/longhorn/longhorn/issues/2749#issuecomment-872072957) This means you have to scale down deployments to expand volumes.
+- Adjusting the defaults in the helm deployment, doesn't adjust them in production. Production is managed with `settings.longhorn.io` objects which are basically a key-value CRD.
+- Longhorn requests by default 12% of your node CPUs for each instance-manager. This can easily exhaust your CPU resources in the cluster. Adjust this setting can only be done **when all your volumes are detached**, which implies scaling down all deployments that use volumes. (The deployment in this directory adjusted the CPU requests to 2%).
+
+
 Links
 ---