Release Notes
TOC
HAMi-WebUI v1.10.2✨ Features / Improvements🐛 Bug Fixes🔒 Security⬆️ Upgrade Notes⚠️ Known Issuesv2.8.3🐛 Bug Fixesv2.8.1Key feature:Bug fixv2.7.1Key feature:Bug fixv2.6.1Bug fixv2.6.0Key feature:Bug fixHAMi-WebUI v1.10.2
HAMi-WebUI release. v1.10.2 is compatible with HAMi v2.7, v2.8 and v2.9 (metrics updated for HAMi 2.9.0).
✨ Features / Improvements
- Cascade filter dropdowns: filter options are now scoped to the current selection.
- Monitor overview charts optimized and new workload insights added.
- Node detail page chart display improved; time picker internationalization fixed.
- Metrics updated for HAMi core 2.9.0 compatibility.
🐛 Bug Fixes
- Make
/metricsscrape-safe and cut page-side query fanout, fixing metrics timeout/OOM and list-page performance on large clusters. - Fix blank page caused by a broken
lodashdependency release (restored lodash 4.17.21).
🔒 Security
- Backend upgraded to Go 1.26.3, clearing 8 Go stdlib CVEs (CVE-2026-33811, -33814, -39820, -39823, -39825, -39826, -39836, -42499).
- Frontend dependencies upgraded (axios 1.16.0, follow-redirects 1.16.0, postcss 8.5.10, qs 6.15.2, ws 8.20.1), clearing 23 Node CVEs.
⬆️ Upgrade Notes
- Supported upgrade path: v1.10.0 → v1.10.2. No breaking changes.
⚠️ Known Issues
- CVE-2026-6993 (go-kratos/kratos v2.7.3, MEDIUM): no fixed upstream release available yet; the backend service is only exposed in-cluster behind the BFF. Planned fix in v1.10.3 once an upstream tagged release is available.
v2.8.3
🐛 Bug Fixes
- fix: handle GetMemoryInfo NOT_SUPPORTED for unified memory GPUs (cherry-pick #1637 to release-v2.8) by @saiyam1814 in #1841
- Fix HAMi-core monitoring not working properly on v2.8.2
- Fix device utilization watcher not launched properly with task not specify
nvidia.com/gpucores
v2.8.1
Key feature:
- Support Huawei Ascend NPU sharing
- Support CDI (Container Device Interface) mode on NVIDIA devices
- Sync with NVIDIA k8s-device-plugin v0.18.0
- Add
hami_build_infoPrometheus metrics and version print - Watch and hot reload TLS certificates without restarting pods
- Support NVIDIA GPU Operator toolkit readiness check
- Support GPUDirect RDMA copy (GDRCopy) and GPUDirect Storage (GDS) configuration
- Support mock device plugin for testing environments
- HAMi-WebUI upgraded to v1.10.0 for Hami v2.8 compatibility; v1.10.0 is compatible with Hami v2.7 and v2.8, while v1.5.0 is not compatible with Hami v2.8
Bug fix
- Fix: HAMi-core updated to fix vLLM-related issues
- Fix: Quota calculation error
- Fix: MIG instance allocation error where scheduler was allocating incorrect MIG instances
- Fix: nvidia-mig-parted upgraded to v0.12.2 for security fixes
- Fix: After removing the device plugin from a GPU node, it could still appear
- Fix: Concurrent map read/write errors
- Fix: Device-NUMA acquisition logic
- Fix: ClusterRoleBinding error when changing release name or chart name
v2.7.1
Key feature:
- Support NVIDIA GPU ResourceQuota(ACP 4.2+)
- Aggregated Scheduling Failure Events
- Make node lock timeout configurable
Bug fix
- Fix: After removing the device plugin from the gpu node, it can still be scheduled in the node.
v2.6.1
Bug fix
- Fix: Device memory not counted properly when allocating with 'cuMallocAsync'
- Fix: Device memory not counted properly when running gpu_burn
- Fix: Segmentation fault on some scenarios
- Fix: Utilization metrics not properly count when using multiple devices
- Fix: Initialization error when using vllm with tp>2
v2.6.0
Key feature:
- Optimize scheduler log
- Support enflame gcu-share
- Support metax GPU and metax sGPU
- Helm chart add checksum annotation for restarting hami component after ConfigMap modification
- Support for using RuntimeClass with nvidia devices
- Add support for profiling via net/http/pprof package
- Add nvidia gpu topoloy score registry to node
- Feat: vGPUmonitor support MigInfo metrics
Bug fix
- Fix stuck in driver 570+
- Fix device memory not counted properly in comfyUI task
- Fix cambricon devices not allocated properly
- Fix wrong log and container request device count error
- Fix vgpu-devices-allocated annotations are inconsistent
- Fix removing node devices from node manager
- Fix: Dynamic GPU partitioning lacks single-GPU-level granularity
- Fix device memory count error on cuMallocAsync
- Fix scheduler crash if a 'mig' task running accidentally on a 'hami-core' GPU
- Fix multi-process device memory count