root/gpustack-ui
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(gpu-service): avoid stringifying unset cpu in the instance form

Browse Source 
`${values.spec?.resources?.cpu}` turned an unset cpu into the literal
string "undefined", which fails k8s quantity validation. Omit cpu when
it has no value instead.
This commit is contained in:
michelia
2026-06-03 17:10:51 +08:00
committed by michela feng
parent c3a779e4c8
commit 820a6cecdd
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/gpu-service/instances/forms/index.tsx
+6 -1
View File
@@ -260,11 +260,16 @@ const GPUServiceInstanceForm: React.FC<InstanceFormProps> = forwardRef(
const cpuNum = unitResourcesParsed?.cpu?.num; const cpuNum = unitResourcesParsed?.cpu?.num;
const ramNum = unitResourcesParsed?.ram?.num; const ramNum = unitResourcesParsed?.ram?.num;
const fallbackCpu = values.spec?.resources?.cpu;
return { return {
cpu: cpu:
accelerator > 0 && cpuNum accelerator > 0 && cpuNum
? `${accelerator * cpuNum}${unitResourcesParsed?.cpu?.unit || ''}` ? `${accelerator * cpuNum}${unitResourcesParsed?.cpu?.unit || ''}`
: `${values.spec?.resources?.cpu}`, : // Don't stringify an unset value — `${undefined}` becomes the
// literal "undefined", which fails k8s quantity validation.
fallbackCpu != null && fallbackCpu !== ''
? `${fallbackCpu}`
: undefined,
ram: ram:
accelerator > 0 && ramNum accelerator > 0 && ramNum
? `${accelerator * ramNum}${unitResourcesParsed?.ram?.unit || ''}` ? `${accelerator * ramNum}${unitResourcesParsed?.ram?.unit || ''}`