Skip to content

VNC token generation API incorrect #119965

Open

Description

@jforce

The following example is wrong now that the feature has gone GA

"https://api.<cluster_fqdn>/apis/token.kubevirt.io/v1alpha1/namespaces/<namespace>/virtualmachines/<vm_name>/vnc?duration=<duration>"

It should be v1 not v1alpha.

"https://api.<cluster_fqdn>/apis/token.kubevirt.io/v1/namespaces/<namespace>/virtualmachines/<vm_name>/vnc?duration=<duration>"

Activity

  1. rudyxx007 commented on Oct 13, 2026

    @rudyxx007

    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:

    1. Which OpenShift Virtualization releases serve token.kubevirt.io/v1, and from which release?
    2. Should v1alpha1 stay in the docs for older releases that don't serve v1?
    3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions