fix: bump fiftyone-app limit, update docker docs, fix md linting

Author: mo-getter

docker/common-services.yaml

@@ -234,10 +234,10 @@ services:
     deploy:
       resources:
         limits:
-          cpus: "0.10"
+          cpus: "0.20"
           memory: 512M
         reservations:
-          cpus: "0.10"
+          cpus: "0.20"
           memory: 512M
     restart: always
 

docker/docs/upgrading.md

@@ -112,15 +112,18 @@ plus a `telemetry-redis` service that buffers the streamed metrics and
 logs.
 
 **Resource impact:**
-Each sidecar reserves `0.10` CPUs and `512M` memory, except the
-`teams-plugins` container which reserves 0.20 CPU. (reservation == limit).
-A default deploy (using `compose.yaml` rather than one of its variants) adds
-two sidecars
-(`fiftyone-app` + `teams-api`), so
-expect roughly **+0.2 CPU** and **+1 GiB memory** in additional
-resource usage, plus the bundled `telemetry-redis` service (`0.10` CPU
-/ `256M` memory reservation, `0.25` / `512M` limits) and its
-`telemetry-redis-data` named volume.
+By default the telemetry requires an additional `0.55` CPU and `1.5Gi` of
+resources used by:
+
+- `telemetry-sidecar` container
+  - `teams-api`: 0.1 CPU and 512 Mi memory
+  - `fiftyone-app`: 0.2 CPU and 512 Mi memory
+- Redis container
+  - 0.25 CPU and 512Mi memory
+
+The additional required resources depends of replica count for each
+deployment.
+The optional deployments may also increase this amount.
 
 ##### Host Requirements
 

helm/docs/upgrading.md

@@ -161,16 +161,19 @@ A default deploy adds three sidecars
 so expect roughly **+600m CPU** and **+1.5 GiB memory** in additional
 resource usage, plus the bundled Redis
 (`250m` CPU / `512Mi` memory, request == limit)
-By default the telemetry requires an additional `850m` CPU and `2Gi` of resources used by
-
-* `telemetry-sidecar` container
-  * `200m` CPU and `512Mi` memory per each replica of 
-    * `teams-api` x 1
-    * `fiftyone-app` x 2
-* Redis container
-  * `250m` CPU and `512Mi` memory
-
-The additional required resources depends of replica count for each deployment. The optional deployments may also increase this amount.
+By default the telemetry requires an additional `850m` CPU and `2Gi` of
+resources used by:
+
+- `telemetry-sidecar` container
+  - `200m` CPU and `512Mi` memory per each replica of
+    - `teams-api` x 1
+    - `fiftyone-app` x 2
+- Redis container
+  - `250m` CPU and `512Mi` memory
+
+The additional required resources depends of replica count for each
+deployment.
+The optional deployments may also increase this amount.
 Tune via `telemetry.sidecar.resources` and `telemetry.redis.resources`.
 Opt into a `PersistentVolumeClaim` with
 `telemetry.redis.persistence.enabled: true`.