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
Hi, I'd like to work on this and open a PR for it.
What I found:
modules/virt-generate-temporary-token-VNC.adoc uses token.kubevirt.io/v1alpha1 in the curl example (the issue says v1alpha, which I assume means v1alpha1).
The published docs I checked (4.14, 4.18, 4.19, 4.21 and 4.22) all show v1alpha1.
Upstream, the vm-console-proxy API package has a v1 version for the token.kubevirt.io group as of v0.8.1 (April 2025).
I haven't been able to verify this against a cluster, so before I open a PR, could someone confirm:
Which OpenShift Virtualization releases serve token.kubevirt.io/v1, and from which release?
Should v1alpha1 stay in the docs for older releases that don't serve v1?
Does the rest of the request path stay the same under v1?
Once I know the versions, I'll open a PR against main listing them so it can be cherry-picked to the right branches. If someone is already working on this, please let me know.
Activity
rudyxx007 commentedon Oct 13, 2026
Hi, I'd like to work on this and open a PR for it.
What I found:
modules/virt-generate-temporary-token-VNC.adocusestoken.kubevirt.io/v1alpha1in the curl example (the issue saysv1alpha, which I assume meansv1alpha1).v1alpha1.vm-console-proxyAPI package has av1version for thetoken.kubevirt.iogroup as of v0.8.1 (April 2025).I haven't been able to verify this against a cluster, so before I open a PR, could someone confirm:
token.kubevirt.io/v1, and from which release?v1alpha1stay in the docs for older releases that don't servev1?v1?Once I know the versions, I'll open a PR against
mainlisting them so it can be cherry-picked to the right branches. If someone is already working on this, please let me know.