LogoTensorFusion Docs
LogoTensorFusion Docs
Homepage

Getting Started

OverviewKubernetes InstallVM/Server Install(K3S)Helm Quick InstallHost/GuestVM InstallTensorFusion Architecture

Application Operations

Create WorkloadAnnotation Usage ScenariosConfigure AutoScalingMigrate Existing WorkloadBest Practices

Customize AI Infra

Production-Grade DeploymentConfig QoS and BillingBring Your Own CloudManaging License

Maintenance & Optimization

Upgrade ComponentsSetup AlertsGPU Live MigrationPreload ModelOptimize GPU Efficiency

Troubleshooting

HandbookTracing/ProfilingQuery Metrics & Logs

Reference

Kubernetes Resource SchemaTensorFusion API Reference

Comparison

Compare with NVIDIA vGPUCompare with MIG/MPSCompare with NVIDIA Run:aiCompare with HAMi
For Developers

Kubernetes Resource Schema

TensorFusion defines 12 custom resources in the API group tensor-fusion.ai, version v1. This page says what each one is for, who normally writes it, and where its field reference is.

How the resources fit together

  • Resource hierarchy: TensorFusionCluster → GPUPool → GPUNode → GPU. You write the cluster and its pools; the controller and the hypervisors create and update nodes and GPUs.
  • Node provisioning: a GPUPool that provisions its own nodes creates GPUNodeClaim objects, each built from a GPUNodeClass.
  • Workloads: a TensorFusionWorkload describes the vGPU resources of an application and may reference a reusable WorkloadProfile. A TensorFusionConnection pairs a client Pod with a remote worker.
  • Policy: SchedulingConfigTemplate, GPUResourceQuota and ProviderConfig hold scheduling policy, namespace quotas and vendor-specific settings.

Infrastructure resources

KindScopeWritten byPurposeField reference
TensorFusionClusterClusterAdmin (the Helm chart creates one)Top-level object. Holds the GPU pools and the cluster-wide component settings.TensorFusionCluster
GPUPoolClusterAdmin, usually through TensorFusionCluster.spec.gpuPoolsA group of GPU nodes with shared capacity, provisioning, oversubscription, QoS pricing and component settings.GPUPool
GPUNodeClusterControllerOne GPU node: its capacity, allocation and phase.GPUNode
GPUClusterHypervisorOne physical GPU: model, capacity, available resources and the Pods running on it.GPU
GPUNodeClassClusterAdminCloud instance template for provisioned nodes: OS image, subnets, security groups, disks, tags and user data.GPUNodeClass
GPUNodeClaimClusterControllerA request for one new node: instance type, zone, capacity type and the TFLOPS, VRAM and GPU count it will add.CRD YAML

Policy and configuration resources

KindScopeWritten byPurposeField reference
SchedulingConfigTemplateClusterAdminPlacement strategy, vertical scaling rules, rebalancing and hypervisor rate-limit parameters. Referenced by a pool.SchedulingConfigTemplate
GPUResourceQuotaNamespacedAdminNamespace-wide totals (TFLOPS, VRAM, worker count) and per-workload maximums and defaults.GPUResourceQuota
ProviderConfigClusterAdmin (the Helm chart creates the NVIDIA one)Per-vendor settings: component images, GPU model catalog, partition templates, and the native resource names TensorFusion takes over.CRD YAML

Workload resources

KindScopeWritten byPurposeField reference
TensorFusionWorkloadNamespacedUser, or the webhook from Pod annotationsvGPU requests and limits, QoS, isolation mode and autoscaling of one application.TensorFusionWorkload
WorkloadProfileNamespacedUser or adminA reusable set of workload settings that workloads and Pod annotations can reference by name.WorkloadProfile
TensorFusionConnectionNamespacedControllerBinds one client Pod to one remote worker and carries the worker's connection URL in its status.TensorFusionConnection

Most users never write these workload resources by hand. Adding workload annotations to a Pod is enough; the webhook creates the rest.

Get the exact schema of your version

The field reference pages on this site are generated from the CRDs and can lag behind a release. GPUNodeClaim and ProviderConfig do not have a page yet. The schema installed in your cluster is always authoritative:

# List the resources
kubectl api-resources --api-group=tensor-fusion.ai

# Describe a field, with type and documentation
kubectl explain gpupool.spec.capacityConfig
kubectl explain tensorfusionworkload.spec --recursive

# Dump the full OpenAPI schema of one CRD
kubectl get crd gpupools.tensor-fusion.ai -o yaml

The source of the CRDs is in the tensor-fusion repository: Go types under api/v1/ and generated YAML under config/crd/bases/.

Further reading

  • Helm chart values
  • TensorFusion DeepWiki, an auto-generated walkthrough of the codebase

TensorFusion Security Whitepaper

Previous

TensorFusion API Reference

Next

Table of Contents

How the resources fit together
Infrastructure resources
Policy and configuration resources
Workload resources
Get the exact schema of your version
Further reading