properly set requests and limits for the deployment

README.md

@@ -97,6 +97,32 @@ Then access it with http://localhost:8080/ and the Django admin with http://loca
 Deployment files are in the `deployment/kustomize` folder and makes use of [Kustomize](https://kustomize.io/) to account for differences between the deployment stages.
 Stages are configured with overlays in `deployment/kustomize/overlays/$environment`.
 
+### Resource Requests and Limits
+
+Resources are configured to comply with APPUiO Cloud's memory-to-CPU ratio of 4096 MiB/core.
+See [APPUiO Cloud documentation](https://docs.appuio.cloud/user/how-to/check-cpu-requests.html) for details.
+
+**Production:**
+
+| Container | CPU Request | Memory Request | CPU Limit | Memory Limit |
+|-----------|-------------|----------------|-----------|--------------|
+| servala   | 500m        | 2Gi            | 2         | 4Gi          |
+
+**Staging:**
+
+| Container        | CPU Request | Memory Request | CPU Limit | Memory Limit |
+|------------------|-------------|----------------|-----------|--------------|
+| servala          | 250m        | 1Gi            | 1         | 2Gi          |
+| ssh-tunnel-dev   | 50m         | 204Mi          | 100m      | 256Mi        |
+| ssh-tunnel-talos | 50m         | 204Mi          | 100m      | 256Mi        |
+
+**Ratio Calculation:**
+
+The ratio is calculated as: `Sum of Memory Requests / Sum of CPU Requests`
+
+- Production: 2048 MiB / 0.5 cores = **4096 MiB/core** ✓
+- Staging: (1024 + 204 + 204) MiB / (0.25 + 0.05 + 0.05) cores = 1432 MiB / 0.35 cores = **4091 MiB/core** ✓
+
 ### Staging
 
 The code is automatically built and deployed on a push to the main branch.