You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also:
Would it make sense to add Pod Allocation Requests under Status to avoid confusion since Pod Allocation Results is also under Status? To keep all pod info in the same area. I believe it would simplify some code as well. As such maybe?
Status:
Pod Allocation Requests:
db18292b-4ddf-44c2-ba6d-797c407191ab:
Pod Ref:
Kind: Pod
Name: emulator-pod-1
Namespace: default
UID: db18292b-4ddf-44c2-ba6d-797c407191ab
Profile: 1g.5gb
Resources:
Requests:
Cpu: 0
Memory: 0
Pod Allocation Results:
db18292b-4ddf-44c2-ba6d-797c407191ab:
Allocation Status:
Allocation Status Controller: ungated
Allocation Status Daemonset: created
Config Map Resource Identifier: 3391ab2f-24a9-4a4e-98c4-9973c5a06cbf
Gpu UUID: GPU-31cfe05c-ed13-cd17-d7aa-c63db5108c24
Mig Placement:
Size: 1
Start: 0
Nodename: kind-e2e-control-plane
Add hierarchy to Node Gpus as such and move under Spec, Node Resources:
Current:
Update:
Also:
Would it make sense to add Pod Allocation Requests under Status to avoid confusion since Pod Allocation Results is also under Status? To keep all pod info in the same area. I believe it would simplify some code as well. As such maybe?
or maybe add it under the same pod?
To put it all together what I am suggesting:
The text was updated successfully, but these errors were encountered: