HOMELAB-1105: Update Tempo values for chart 1.24.2 #229
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plane/HOMELAB-1105-upgrade-tempo-chart"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Updates Tempo Helm values for chart 1.24.2 compatibility and adds
host.nameresource_dimensions support.Breaking changes addressed
server.http_listen_port: 3100prevents Grafana datasource breakagehost.namefor dashboard filteringRelated
Worker exits on startup without SANDBOX_NAME (needed for LifecycleWorkflow ID: sandbox-lifecycle-{name}). SANDBOX_MODE was also missing from the base chart. SANDBOX_NAME is derived from the existing sandbox.name value field. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>- Use label selector {namespace!="outline"} instead of complex expressions - Excludes metrics from outline namespace to prevent false alerts - Resolves HOMELAB-705 WAL archive delay alert for intentionally disabled backupswk-01 is capped at the kubelet default (110 pods/node) and, with wk-02 cordoned pending HDD replacement, new deploys (observed on HOMELAB-954 WorkAdventure) hit FailedScheduling / "Too many pods". Raise the cap via the worker config patch so there's headroom for the current stack (harbor, temporal, longhorn, monitoring, etc.) plus new workloads. Adds `kubelet.extraConfig.maxPods = 150` to the worker_config_patch local. Applies to every worker via the existing talos_machine_configuration_apply.worker loop. Talos reloads kubelet in place — no full node reboot. Apply path (Atlantis is offline, manual for now): cd prod/terraform && terraform plan -out=956.tfplan terraform apply 956.tfplan Verify after apply: kubectl get node prod-wk-01 -o jsonpath='{.status.capacity.pods}{"\n"}' # expect: 150 Unblocks HOMELAB-954 (WorkAdventure pods currently Pending).Today's EROFS storm: with both ZFS pools degraded on daytona (hdd-mirror single-disk after HOMELAB-860 sdb detach, ssd-mirror has one UNAVAIL Bestoss SSD), the underlying disk sustains ~30 MB/s. concurrentReplicaRebuildPerNodeLimit=5 saturated the hdd-mirror spindle, engine sync writes timed out, kernel marked multiple PVCs read-only (postgres CNPGs, harbor-redis, plane-rabbitmq Mnesia). Throttle to 1 in-flight rebuild per node so the disk can serve foreground sync writes alongside replica rebuilds. Disable auto-balance during the recovery window — it's already inert while volumes are degraded ("Cannot auto-balance volume in degraded state" log spam) but remove the controller pressure entirely. Restore to concurrency=2 + replicaAutoBalance=best-effort once both ZFS pools are resilvered and the rebuild backlog has drained. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>acc9a4526cc85f6823fc