Discovery fails when ApiResourceList is not apiVersion v1 about kube HOT 5 CLOSED

My guess is that this line here is wrong and should simply be "v1". instead of version https://github.com/kubevirt/kubevirt/blame/e53b1249f073ffab068037973a914303082925c9/pkg/virt-api/api.go#L584C5-L584C37

from kube.

Happened to me too with the location comment :D

Anyhow, I initially thought that simply having Kubevirt and using Kube.rs was enough to cause this bug. But as it is only when using Dynamic discovery and it looks like a sincere oversight on KubeVirt side (vs a v1alpha3 being used in the past), I think this bug could be closed without any further action.

from kube.

IIRC from the kubevirt thread i think possibly kubevirt was confusing the version for the apiresource kind with the version of their own apigroup.

If true, then that is probably something that needs to be raised with them. Kind of surprised this works at all on the golang side.

from kube.

Unfortunately I don't seem to have access to the discord thread you mentioned. But a simple mistake seems the most plausible. I also raised it with them kubevirt/kubevirt#10899.

from kube.

That looks like a good change upstream to me. Thanks for digging into this.

  }, Error("invalid value: string \"v1alpha3\", expected v1", line: 3, column: 25)
  Error: Error deserializing response

  Caused by:
      invalid value: string "v1alpha3", expected v1 at line 3 column 25

EDIT: accidentally replied this to upstream repo 🤦

from kube.