-
Notifications
You must be signed in to change notification settings - Fork 44
Description
Customer who has one HP cluster running getting two dictionaries output
hyperpod get-clusters --region us-east-2
Updated context arn:aws:eks:us-east-2:108782055435:cluster/zelda-sm-hp-eks-no-git in /tmp/kubeconfig
[
{
"Cluster": "zelda-sm-hp-eks-no-git",
"InstanceType": "ml.g5.12xlarge",
"TotalNodes": 4,
"AcceleratorDevicesAvailable": 16,
"NodeHealthStatus=Schedulable": 4,
"DeepHealthCheckStatus=Passed": 4
},
{
"Cluster": "zelda-sm-hp-eks-no-git",
"InstanceType": "ml.m5.2xlarge",
"TotalNodes": 1,
"AcceleratorDevicesAvailable": "N/A",
"NodeHealthStatus=Schedulable": 1,
"DeepHealthCheckStatus=Passed": "N/A"
}
]
This is probably due to the two instance groups in the clusters. It created confusion to customer and we should reformat the output to only have one cluster name