Skip to main content

HAMi Enterprise 2.10.0-r1

The HAMi Enterprise 2.10 series improves shared compute-resource management, device support, and operations integrations. It introduces optional resource-pool management while retaining Enterprise GPU allocation management and GPU memory auto-expansion. v2.10.0-r1 also incorporates open-source HAMi dynamic MIG, combined GPU scheduling policies, init-container resource accounting, multi-device quota improvements, and stability fixes.

Version information​

ItemValue
Enterprise releaseHAMi Enterprise v2.10.0-r1
Release date2026-08-28
Enterprise upgrade baselinev2.9.0-r3 (the last release in the 2.9 series)
Open-source baselineHAMi v2.10.0
Helm Charthami-enterprise, version 2.10.0-r1
Chart appVersion2.10.0-r1
Default component image tagv2.10.0-r1

Software changes​

Changes compared with Enterprise v2.9.0-r3​

Enterprise license management, NVIDIA GPU allocation management, GPU memory auto-expansion, and Alibaba PPU integration were already available in Enterprise 2.9 and remain available in this release.

Monitoring and collection improvements​

  • Adds workload information for compute-allocation mode, memory overcommit, and auto-expansion status to help platforms display resource configuration and feature enablement.
  • Fixes metric attribution issues in some workloads containing init containers.
  • Updates container-memory and MIG monitoring metrics. Review metrics and labels used by existing dashboards and alert rules; see “Configuration migration and platform integration.”

Device support and stability fixes​

  • Fixes mode matching for some Ascend vNPU workloads and improves memory-request handling.
  • Fixes cleanup of residual data in scenarios such as task failures.
  • Synchronizes open-source scheduling, device-support, quota, and concurrency improvements, including dynamic MIG and combined GPU scheduling policies. See “Upstream changes included in this release” and the referenced PRs.

Enterprise extensions compared with open-source HAMi v2.10.0​

Resource-pool management (optional in the 2.10 series)​

The 2.10 series introduces optional resource-pool management. It organizes device resources by team or business unit and configures the namespaces that can use each resource pool, helping manage compute-resource access in shared clusters.

Resource-pool management is disabled by default and is not enabled automatically when the v2.10.0-r1 main Chart is installed. Install and enable the companion components according to their deployment instructions.

Enterprise license management​

  • Manages licenses by device instance or device-model count to support deployments of different sizes.
  • Provides license-validity status, remaining validity, and error events to help plan renewals and investigate issues.
  • License coverage varies by device type; select the license plan that matches the deployment.

GPU resource usage and memory auto-expansion​

  • Provides Enterprise NVIDIA GPU allocation management with container-level device allocation and memory and compute limits.
  • Supports adjusting memory limits as needed for NVIDIA GPU workloads with auto-expansion enabled, for example when memory demand grows at runtime.
  • Expansion is constrained by remaining device memory and currently applies to regular workload containers, not init containers.

Heterogeneous devices and platform integration​

  • Provides resource scheduling, quota management, license integration, and deployment configuration for Alibaba PPU.
  • AWS Neuron resource accounting and AMD device-type identifiers differ from the open-source baseline. Verify the relevant accounting semantics and type mappings when integrating with an existing resource-management platform.
  • Adds Enterprise monitoring information for resource configuration, auto-expansion status, and license validity, and extends CDI integration settings for existing operations platforms and container runtimes.

Upstream changes included in this release​

v2.10.0-r1 includes the following major open-source features and fixes. See the referenced PRs for background; Enterprise configuration requirements and differences are described in “Upgrade notes.”

Scheduling and resource allocation​

ChangeImpact on usage and integrationUpstream PR
Init-container resource accountingImproves resource accounting and release for init and workload containers. The subsequent slot-count fix is not included; see “Known differences from the open-source baseline.”#1773
GPU mutual-exclusion scheduling policyAdds the mutex policy for exclusive GPU allocation.#2011
Combined GPU scheduling policiesCombines multiple GPU scheduling policies and applies them in configured order.#2621
PodGroup supportImproves scheduling retries for tasks in a group and supports Kubernetes SchedulingGroup recognition.#2066, #2206
Scheduling evaluation on template nodesEvaluates whether a task can be scheduled on a template node, providing a basis for integration with scale-up decisions. A complete autoscaling solution still requires separate integration.#2046
NVIDIA NUMA informationOptionally provides vGPU NUMA topology information; disabled by default.#2065
Dynamic MIGDynamically allocates and releases MIG instances based on task requirements and improves MIG profile management.#2378
RTX PRO 6000 Blackwell MIGAdds dynamic MIG support and profile configuration for this model.#2135

Device support​

ChangeImpact on usage and integrationUpstream PR
AMD vGPUSupports resource requests and allocation for AMD virtual devices.#2290
Biren devicesAdds device recognition and scheduling support for Biren hardware.#1711
Ascend hybrid-mode schedulingWorkloads without an explicit mode can match both vNPU-template and HAMi-core nodes.#2035
Ascend 910C templatesAdds resource profiles such as vir05_1c_16g and vir10_3c_32g.#2005
Ascend memory requestsPreserves the user-requested memory value instead of rounding it to a template value during parsing.#2696

Quotas and stability​

ChangeImpact on usage and integrationUpstream PR
Zero quotas and quota updatesTreats an explicitly configured zero quota as zero capacity and improves limit handling after quota updates.#2313, #2386
Multi-device quota checksImproves quota validation across device backends, including Cambricon percentage-memory and full-card memory requests.#2347, #2536
Release resources after scheduling failuresFixes stale allocation records that could leave resources occupied after some scheduling failures.#1927
Concurrent scheduling stabilityFixes data races when Pods and node information are processed concurrently.#2055, #2472, #2333, #2504
Recover device schedulingFixes release of node locks for Cambricon devices to avoid affecting subsequent scheduling.#2329
Read monitoring dataImproves handling of abnormal or unready data, reducing interference from unrelated files and invalid device information during collection.#2529, #2503, #2465

Chart changes​

Deployment and runtime integration​

  • Adds an installation setting for the Enterprise NVIDIA GPU allocation mode; the default behavior is unchanged and can be configured for the deployment.
  • Extends CDI configuration to support a custom device-identifier prefix and improves dynamic MIG device integration.
  • Completes PPU scheduling resource configuration to improve deployment integration for the existing PPU capability.
  • Improves deployment health checks so abnormal tasks in other namespaces do not affect the check.

Upstream installation-configuration changes​

ChangeImpact on usage and integrationUpstream PR
Device Plugin security configurationConfigures the Device Plugin security context through Helm values to fit cluster security policies.#1887
Custom device configurationProvides a complete device configuration through device-config.content for consistent management by integrators.#2277

Upgrade notes​

Packages and component selection​

Obtain the Helm package, component images, and component manifest for this release through the agreed delivery channel. Use the companion delivery manifest when deploying and recording software versions.

When introducing resource pools, plan resource access by team or business unit and deploy the companion components.

Configuration migration and platform integration​

  • Custom device configuration: device-config.content replaces the entire default device configuration; it does not merge individual fields. If you use this setting or a custom device-configuration file in the Chart, maintain the Enterprise device options required by your deployment.
  • Monitoring integrations: When upgrading from Enterprise 2.9, hami_container_device_memory_bytes no longer has the context_size, module_size, buffer_size, and offset labels. Use the corresponding hami_vgpu_memory_*_bytes metrics for memory breakdowns. Labels on hami_mig_device_info have also changed; update dashboards and alert rules that use the old labels. When integrating AMD or AWS Neuron, also verify Enterprise device-type mappings and accounting semantics.
  • Optional features: NVIDIA NUMA topology information is disabled by default and can be enabled with devicePlugin.enableNumaTopology as needed. GPU memory auto-expansion must be enabled for the relevant workload, and sufficient allocatable memory must be available.
  • Ascend runtime environment: Enterprise HAMi-core runtime startup requirements differ from the open-source version. Use the Enterprise companion runtime and configuration for deployment. See upstream change #2062.
  • DRA integration: Enterprise retains an optional DRA component, disabled by default. Open-source HAMi has removed that component from its main Chart, so its installation layout cannot be copied directly. See upstream change #2038.

Known differences from the open-source baseline​

The following open-source v2.10.0 features and fixes are not included in Enterprise v2.10.0-r1; account for these limitations when integrating.

ScenarioLimitation in this releaseUpstream PR
Device requests from init containersInit-container resource accounting is supported, but the subsequent device-slot-count fix is not included.#2623
Stop assigning new tasks to one GPUDoes not yet include dynamic blocking of new allocations to an individual GPU through hami.io/device-cordon.#2298
Quota monitoringDoes not provide a separate hami_resource_quota_limit metric. Monitoring rules should not depend on it.#2715
Device count becomes zeroDoes not yet include the fix that clears stale device information when a device reports zero. Check whether displayed resources match actual device state.#2550
Invalid scheduling API requestsDoes not yet include validation for Filter requests that lack Pod information. Integrators should ensure requests are complete.#2689

See the Chart and appVersion mapping or the software center.

Values reference​

The following parameter descriptions are taken from the README bundled with the Chart 2.10.0-r1 release package and are preserved as published. Use this version's values.yaml as the source of default configuration.

Expand values table
KeyTypeDefaultDescription
birenResourceNamestring"birentech.com/gpu"Biren GPU resource name
dcuResourceCoresstring"hygon.com/dcucores"Hygon DCU cores resource name
dcuResourceMemstring"hygon.com/dcumem"Hygon DCU memory resource name
dcuResourceNamestring"hygon.com/dcunum"Hygon DCU resource name
device-config.contentstring""
devicePlugin.cdiVendorstring""CDI vendor for generated specs and device annotations (default: k8s.device-plugin.nvidia.com)
devicePlugin.createRuntimeClassboolfalseWhether to create runtime class
devicePlugin.deviceCoreScalingint1Device core scaling factor
devicePlugin.deviceListStrategystring"envvar"Device list strategy. Supported values: envvar, volume-mounts, cdi-annotations
devicePlugin.deviceMemoryScalingint1Device memory scaling factor
devicePlugin.deviceSplitCountint10Number of slices to split each GPU into
devicePlugin.disablecorelimitstring"false"Disable core limit
devicePlugin.enableNumaTopologyboolfalseAdvertise the physical GPU's NUMA node on each vGPU replica
devicePlugin.enabledbooltrueEnable device plugin
devicePlugin.extraArgslist["-v=4"]Extra arguments for device plugin
devicePlugin.extraEnvsobject{}Extra environment variables for device plugin
devicePlugin.gdrcopyEnabledboolfalseEnable GDRCopy
devicePlugin.gdsEnabledboolfalseEnable GDS
devicePlugin.gpuOperatorToolkitReady.enabledboolfalseEnable GPU operator toolkit ready check
devicePlugin.gpuOperatorToolkitReady.hostPathstring"/run/nvidia/validations"Host path for GPU operator toolkit ready check
devicePlugin.gpuOperatorToolkitReady.securityContextobject{"privileged":true,"runAsUser":0}Security context for the toolkit-ready init container
devicePlugin.hostNetworkboolfalseShare the host network namespace with the device plugin pod
devicePlugin.hostPIDbooltrueShare the host PID namespace with the device plugin pod
devicePlugin.image.pullPolicystring"IfNotPresent"Device plugin image pull policy
devicePlugin.image.pullSecretslist[]Specify docker-registry secret names as an array
devicePlugin.image.registrystring"ghcr.io"Device plugin image registry
devicePlugin.image.repositorystring"dynamia-ai/hami-enterprise"Device plugin image repository
devicePlugin.image.tagstring""Device plugin image tag (immutable tags are recommended)
devicePlugin.libPathstring"/usr/local/vgpu"Library path for vGPU
devicePlugin.migStrategystring"none"MIG strategy. Supported values: none, single, mixed
devicePlugin.mofedEnabledboolfalseEnable Mellanox OFED
devicePlugin.monitor.ctrPathstring"/usr/local/vgpu/containers"Container path for monitor
devicePlugin.monitor.extraArgslist["-v=4"]Extra arguments for monitor
devicePlugin.monitor.extraEnvsobject{}Extra environment variables for monitor
devicePlugin.monitor.image.pullPolicystring"IfNotPresent"Monitor image pull policy
devicePlugin.monitor.image.pullSecretslist[]Specify docker-registry secret names as an array
devicePlugin.monitor.image.registrystring"ghcr.io"Monitor image registry
devicePlugin.monitor.image.repositorystring"dynamia-ai/hami-enterprise"Monitor image repository
devicePlugin.monitor.image.tagstring""Monitor image tag (immutable tags are recommended)
devicePlugin.monitor.resourcesobject{}Resources for monitor container
devicePlugin.monitor.resyncIntervalstring"5m"Resync interval for monitor
devicePlugin.monitor.securityContextobject{"allowPrivilegeEscalation":false,"capabilities":{"add":["SYS_ADMIN"],"drop":["ALL"]}}Security context for the monitor container
devicePlugin.nodeConfiguration.configstring"{\n \"nodeconfig\": [\n {\n \"name\": \"your-node-name\",\n \"operatingmode\": \"hami-core\",\n \"devicememoryscaling\": 1,\n \"devicesplitcount\": 10,\n \"preconfigureddevicememory\": 0,\n \"enablenumatopology\": false,\n \"migstrategy\": \"none\",\n \"filterdevices\": {\n \"uuid\": [],\n \"index\": []\n },\n \"enablegetpreferredallocation\": false\n }\n ]\n}\n"Node configuration for device plugin. If set, overrides the default config.json
devicePlugin.nodeConfiguration.externalConfigNamestring""Name of an existing ConfigMap to use for node configuration
devicePlugin.nvidiaDriverRootstring""Root path for NVIDIA driver
devicePlugin.nvidiaHookPathstring""Path for NVIDIA hook
devicePlugin.nvidiaNodeSelectorobject{"gpu":"on"}Node selector for NVIDIA device plugin
devicePlugin.passDeviceSpecsEnabledboolfalseEnable passing device specs
devicePlugin.pluginPathstring"/var/lib/kubelet/device-plugins"Path for device plugin socket
devicePlugin.podAnnotationsobject{}Annotations for device plugin pod
devicePlugin.preConfiguredDeviceMemoryint0Pre-configured device memory in MB for GPUs that don't support memory query. Set to 0 for auto-detection
devicePlugin.resourcesobject{}Resources for device plugin container
devicePlugin.runtimeClassNamestring""Runtime class name to be used by the device plugin
devicePlugin.securityContextobject{"allowPrivilegeEscalation":true,"capabilities":{"add":["SYS_ADMIN"],"drop":["ALL"]},"privileged":true}Security context for the device plugin container
devicePlugin.service.annotationsobject{}Annotations for device plugin service
devicePlugin.service.httpPortint31992HTTP port for device plugin service
devicePlugin.service.labelsobject{}Labels for device plugin service
devicePlugin.service.typestring"NodePort"Service type for device plugin
devicePlugin.tolerationslist[]Tolerations for device plugin pod
devicePlugin.updateStrategy.rollingUpdate.maxUnavailableint1Maximum unavailable pods during update
devicePlugin.updateStrategy.typestring"RollingUpdate"Update strategy for device plugin DaemonSet
devices.alibaba.customresourceslist["alibaba.com/ppu","alibaba.com/ppu-memory","alibaba.com/gpu-core"]Custom resource definitions for Alibaba devices
devices.alibaba.enabledbooltrueEnable Alibaba PPU device
devices.alibaba.ppuCorePolicystring"default"PPU core policy for Alibaba devices
devices.amd.customresourceslist["amd.com/gpu","amd.com/gpumem","amd.com/gpucores"]Custom resource definitions for AMD devices
devices.ascend.customresourceslist["huawei.com/Ascend910A","huawei.com/Ascend910A-memory","huawei.com/Ascend910A-core","huawei.com/Ascend910B2","huawei.com/Ascend910B2-memory","huawei.com/Ascend910B2-core","huawei.com/Ascend910B3","huawei.com/Ascend910B3-memory","huawei.com/Ascend910B3-core","huawei.com/Ascend910B4","huawei.com/Ascend910B4-memory","huawei.com/Ascend910B4-core","huawei.com/Ascend910B4-1","huawei.com/Ascend910B4-1-memory","huawei.com/Ascend910B4-1-core","huawei.com/Ascend310P","huawei.com/Ascend310P-memory","huawei.com/Ascend310P-core","huawei.com/Ascend910C","huawei.com/Ascend910C-memory","huawei.com/Ascend910C-core"]Custom resource definitions for Ascend devices
devices.ascend.enabledboolfalseEnable Ascend device plugin
devices.ascend.extraArgslist[]Extra arguments for Ascend device plugin
devices.ascend.hamiVnpuCoreboolfalseEnable soft-partitioning based on hami-vnpu-core (node-level annotation takes higher priority)
devices.ascend.imagestring""Ascend device plugin image
devices.ascend.imagePullPolicystring"IfNotPresent"Image pull policy for Ascend device plugin
devices.ascend.nodeSelectorobject{"ascend":"on"}Node selector for Ascend device plugin
devices.ascend.runtimeClassNamestring""Runtime class name for Ascend NPU pods
devices.ascend.tolerationslist[]Tolerations for Ascend device plugin
devices.awsneuron.customresourceslist["aws.amazon.com/neuron","aws.amazon.com/neuroncore"]Custom resource definitions for AWS Neuron devices
devices.biren.customresourceslist["birentech.com/gpu"]Custom resource definitions for Biren devices
devices.biren.enabledbooltrueEnable Biren device plugin
devices.enflame.customresourceslist["enflame.com/drs-gcu","enflame.com/gcu-memory","enflame.com/gcu-core","enflame.com/gcu","enflame.com/vgcu","enflame.com/vgcu-percentage"]Custom resource definitions for Enflame devices
devices.enflame.enabledbooltrueEnable Enflame device plugin
devices.iluvatar.customresourceslist["iluvatar.ai/BI-V100-vgpu","iluvatar.ai/BI-V100.vCore","iluvatar.ai/BI-V100.vMem","iluvatar.ai/BI-V150-vgpu","iluvatar.ai/BI-V150.vCore","iluvatar.ai/BI-V150.vMem","iluvatar.ai/MR-V100-vgpu","iluvatar.ai/MR-V100.vCore","iluvatar.ai/MR-V100.vMem","iluvatar.ai/MR-V50-vgpu","iluvatar.ai/MR-V50.vCore","iluvatar.ai/MR-V50.vMem"]Custom resource definitions for Iluvatar devices
devices.iluvatar.enabledboolfalseEnable Iluvatar device plugin
devices.kunlun.customresourceslist["kunlunxin.com/xpu","kunlunxin.com/vxpu","kunlunxin.com/vxpu-memory"]Custom resource definitions for Kunlun devices
devices.kunlun.enabledbooltrueEnable Kunlun device plugin
devices.mthreads.customresourceslist["mthreads.com/vgpu"]Custom resource definitions for MThreads devices
devices.mthreads.enabledbooltrueEnable MThreads device plugin
devices.nvidia.gpuCorePolicystring"default"GPU core policy for NVIDIA devices
devices.nvidia.libCudaLogLevelint2libCUDA log level
devices.vastai.customresourceslist["vastaitech.com/va"]Custom resource definitions for Vastai devices
devices.vastai.enabledbooltrueEnable Vastai device plugin
dra.enabledboolfalseEnable DRA (Dynamic Resource Allocation)
enflameResourceNameDRSGCUstring"enflame.com/drs-gcu"Enflame DRS GCU resource name
enflameResourceNameGCUCorestring"enflame.com/gcu-core"Enflame GCU core resource name
enflameResourceNameGCUMemorystring"enflame.com/gcu-memory"Enflame GCU memory resource name
enflameResourceNameVGCUstring"enflame.com/vgcu"Enflame VGCU resource name
enflameResourceNameVGCUPercentagestring"enflame.com/vgcu-percentage"Enflame VGCU percentage resource name
fullnameOverridestring""Override the fullname of the chart
global.annotationsobject{}Global annotations to add to all resources
global.gpuHookPathstring"/usr/local"Path for GPU hook installation on nodes
global.imagePullSecretslist[]Global Docker image pull secrets
global.imageRegistrystring""Global Docker image registry
global.imageTagstring"v2.10.0-r1"Global image tag for HAMi Enterprise components
global.labelsobject{}Global labels to add to all resources
global.managedNodeSelectorobject{"usage":"gpu"}Node selector configuration for managed GPU nodes
global.managedNodeSelectorEnableboolfalseEnable managed node selector for GPU nodes
hami-dra.drivers.nvidia.containerDriverbooltrueEnable container driver for NVIDIA DRA
hami-dra.drivers.nvidia.enabledbooltrueEnable NVIDIA DRA driver
hami-dra.drivers.nvidia.image.repositorystring"ghcr.io/project-hami/k8s-dra-driver"NVIDIA DRA driver image repository
hami-dra.drivers.nvidia.image.tagstring"main"NVIDIA DRA driver image tag
hami-dra.monitor.enabledbooltrueEnable monitor for hami-dra
kunlunResourceNamestring"kunlunxin.com/xpu"Kunlun XPU resource name
kunlunResourceVCountNamestring"kunlunxin.com/vxpu"Kunlun virtual XPU count resource name
kunlunResourceVMemoryNamestring"kunlunxin.com/vxpu-memory"Kunlun virtual XPU memory resource name
legacyMetricsboolfalseEnable legacy metrics
metaxResourceCorestring"metax-tech.com/vcore"Metax sGPU core resource name
metaxResourceMemstring"metax-tech.com/vmemory"Metax sGPU memory resource name
metaxResourceNamestring"metax-tech.com/sgpu"Metax sGPU resource name
metaxsGPUTopologyAwarestring"false"Enable Metax sGPU topology awareness
mluResourceCoresstring"cambricon.com/mlu.smlu.vcore"MLU cores resource name
mluResourceMemstring"cambricon.com/mlu.smlu.vmemory"MLU memory resource name
mluResourceNamestring"cambricon.com/vmlu"MLU resource name
mockDevicePlugin.enabledboolfalseEnable mock device plugin
mockDevicePlugin.image.pullPolicystring"IfNotPresent"Mock device plugin image pull policy
mockDevicePlugin.image.pullSecretslist[]Specify docker-registry secret names as an array
mockDevicePlugin.image.registrystring"docker.io"Mock device plugin image registry
mockDevicePlugin.image.repositorystring"projecthami/mock-device-plugin"Mock device plugin image repository
mockDevicePlugin.image.tagstring"1.0.1"Mock device plugin image tag
nameOverridestring""Override the chart name
namespaceOverridestring""Override the namespace
podSecurityPolicy.enabledboolfalseEnable PodSecurityPolicy
prometheus.enabledboolfalseEnable Prometheus metrics
resourceCoresstring"nvidia.com/gpucores"NVIDIA GPU cores resource name
resourceMemstring"nvidia.com/gpumem"NVIDIA GPU memory resource name
resourceMemPercentagestring"nvidia.com/gpumem-percentage"NVIDIA GPU memory percentage resource name
resourceNamestring"nvidia.com/gpu"NVIDIA GPU resource name
resourcePrioritystring"nvidia.com/priority"NVIDIA GPU priority resource name
scheduler.admissionWebhook.customURL.enabledboolfalseEnable custom webhook URL
scheduler.admissionWebhook.customURL.hoststring"127.0.0.1"Webhook host (must be an endpoint using https)
scheduler.admissionWebhook.customURL.pathstring"/webhook"Webhook path
scheduler.admissionWebhook.customURL.portint31998Webhook port
scheduler.admissionWebhook.enabledbooltrueEnable admission webhook. If disabled, pods must be configured with correct schedulerName manually
scheduler.admissionWebhook.failurePolicystring"Ignore"Failure policy for webhook
scheduler.admissionWebhook.manageNamespaceSelectorbooltrueWhether the chart renders and manages the webhook's namespaceSelector field
scheduler.admissionWebhook.namespaceSelectorobject{"matchExpressions":[],"matchLabels":{}}Namespace selector for webhook
scheduler.admissionWebhook.objectSelectorobject{"matchExpressions":[]}Object selector for webhook
scheduler.admissionWebhook.reinvocationPolicystring"Never"Reinvocation policy for webhook
scheduler.admissionWebhook.whitelistNamespaceslist[]Namespaces that the webhook will not be applied to
scheduler.certManager.enabledboolfalseEnable cert-manager for TLS certificate generation
scheduler.defaultSchedulerPolicy.gpuSchedulerPolicystring"spread"GPU-level scheduling policy. Supported values: binpack, spread
scheduler.defaultSchedulerPolicy.nodeSchedulerPolicystring"binpack"Node-level scheduling policy. Supported values: binpack, spread
scheduler.extender.extraArgslist["--debug","-v=4"]Extra arguments for scheduler extender
scheduler.extender.image.pullPolicystring"IfNotPresent"Scheduler extender image pull policy
scheduler.extender.image.pullSecretslist[]Specify docker-registry secret names as an array
scheduler.extender.image.registrystring"ghcr.io"Scheduler extender image registry
scheduler.extender.image.repositorystring"dynamia-ai/hami-enterprise"Scheduler extender image repository
scheduler.extender.image.tagstring""Scheduler extender image tag (immutable tags are recommended)
scheduler.extender.resourcesobject{}Resources for scheduler extender container
scheduler.forceOverwriteDefaultSchedulerbooltrueForce overwrite the default scheduler name in pods when it equals the K8s default scheduler name
scheduler.kubeScheduler.enabledbooltrueWhether to run kube-scheduler container in the scheduler pod
scheduler.kubeScheduler.extraArgslist["--policy-config-file=/config/config.json","-v=4"]Extra arguments for kube-scheduler (legacy config format)
scheduler.kubeScheduler.extraNewArgslist["--config=/config/config.yaml","-v=4"]Extra arguments for kube-scheduler (new config format)
scheduler.kubeScheduler.image.pullPolicystring"IfNotPresent"kube-scheduler image pull policy
scheduler.kubeScheduler.image.pullSecretslist[]Specify docker-registry secret names as an array
scheduler.kubeScheduler.image.registrystring"registry.cn-hangzhou.aliyuncs.com"kube-scheduler image registry
scheduler.kubeScheduler.image.repositorystring"google_containers/kube-scheduler"kube-scheduler image repository
scheduler.kubeScheduler.image.tagstring""kube-scheduler image tag (immutable tags are recommended)
scheduler.kubeScheduler.resourcesobject{}Resources for kube-scheduler container
scheduler.leaderElectbooltrueEnable leader election for scheduler
scheduler.livenessProbeboolfalseEnable liveness probe for scheduler
scheduler.metricsBindAddressstring":9395"Address to bind metrics server
scheduler.nodeLockExpirestring"5m"Node lock expiration time
scheduler.nodeNamestring""Node name for scheduler pod. If installing as default scheduler, set this to skip the schedule workflow
scheduler.overwriteEnvstring"false"Overwrite environment variables
scheduler.patch.enabledbooltrueEnable kube-webhook-certgen patch job
scheduler.patch.image.pullPolicystring"IfNotPresent"kube-webhook-certgen image pull policy
scheduler.patch.image.pullSecretslist[]Specify docker-registry secret names as an array
scheduler.patch.image.registrystring"docker.io"kube-webhook-certgen image registry
scheduler.patch.image.repositorystring"jettech/kube-webhook-certgen"kube-webhook-certgen image repository
scheduler.patch.image.tagstring"v1.5.2"kube-webhook-certgen image tag
scheduler.patch.imageNew.pullPolicystring"IfNotPresent"New kube-webhook-certgen image pull policy
scheduler.patch.imageNew.pullSecretslist[]Specify docker-registry secret names as an array
scheduler.patch.imageNew.registrystring"docker.io"New kube-webhook-certgen image registry
scheduler.patch.imageNew.repositorystring"liangjw/kube-webhook-certgen"New kube-webhook-certgen image repository
scheduler.patch.imageNew.tagstring"v1.1.1"New kube-webhook-certgen image tag
scheduler.patch.nodeSelectorobject{}Node selector for patch job
scheduler.patch.podAnnotationsobject{}Annotations for patch job pod
scheduler.patch.priorityClassNamestring""Priority class name for patch job
scheduler.patch.runAsUserint2000User ID to run patch job as
scheduler.patch.tolerationslist[]Tolerations for patch job
scheduler.podAnnotationsobject{}Annotations for scheduler pod
scheduler.replicasint1Number of scheduler replicas (only effective when leaderElect is true)
scheduler.service.annotationsobject{}Annotations for scheduler service
scheduler.service.httpPortint443HTTP port for scheduler service
scheduler.service.httpTargetPortint443Target port for HTTP
scheduler.service.labelsobject{}Labels for scheduler service
scheduler.service.monitorPortint31993Monitoring port for scheduler service
scheduler.service.monitorTargetPortint9395Target port for monitoring
scheduler.service.schedulerPortint31998NodePort for scheduler HTTP
scheduler.service.typestring"NodePort"Service type for scheduler
scheduler.tolerationslist[]Tolerations for scheduler pod
scheduler.useDownwardbooltrueWhether to enable useDownward in the generated scheduler device config for NVIDIA devices
schedulerNamestring"hami-scheduler"Name of the scheduler
vastaiResourceNamestring"vastaitech.com/va"Vastai resource name