https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
p
kubectl get vmi will give you the nodename
m
Aye, I was hoping to utilize the web API only
p
Web api?
m
Yes, for harvester
p
In the example, there seems to be a nodename
m
Problem with that is that endpoint doesn't appear to exist for me. for example, I can view the default namespace - using https://harvester.local/v1/namespaces/default but adding the /virtualmachineinstances does not work. I'm on the most recent non-dev build, too.
p
Works for me on 1.3.2 Also you're using the wrong URL it seems as the vmis are part of kubevirt and not the standard Kubernetes api
Replace default with the namespace of your choosing
m
aight, let me give that a shot - thanks!
I should probably do a bug report then because of how it's done in the api key creation points me to using the url I have
p
Ah, right, I understand. But yeah, that URL would only be for objects native to Kubernetes like pods, deployments, services etc...
p
@clever-mouse-42560 Do you have insight on this? How do we show the host of a VM in the GUI page?
p
On the GUI dashboard, the VM tab lists the VMs and the supporting node, no?
p
Hi, I checked with a UI engineer, can you see if this helps? 
v1/harvester/kubevirt.io.virtualmachineinstances
endpoint can know which VM running on which node.
See 
data[x].status.nodeName
or 
data[x].metadata.labels.nodeName
c
Confirming that the 
nodeName
is 
vmiObject.status.nodeName
m
I'll give those a shot, thanks!
Open in Slack
PreviousNext
Powered by