Skip to content

Show control plane version in rad version #8953

Closed

Description

@willtsai

Overview of feature request

Currently, the rad version command only displays the version of the Radius CLI installed locally and not the version of the Radius control plane running in the cluster that the user is pointed to:

% rad version
RELEASE   VERSION   BICEP     COMMIT
0.44.0    v0.44.0   0.33.93   1dd17270ec9bc9e764f314fa62c248406034edda

Since the CLI version is intentionally independent of the version of the control plane running in the cluster, showing only the version of the CLI is a confusing UX as it does not specify to the user whether they are seeing the version of the CLI or control plane being displayed.

To mitigate this, rad version should be clear in displaying both the version of the CLI installed on the user's machine and control plane running on the cluster.

Acceptance criteria

When a user runs the rad version command, both the CLI version installed on the user's machine
and the control plane version running on the cluster they are currently pointed at should be displayed, e.g.

% rad version
CLI-RELEASE   CLI-VERSION   BICEP     COMMIT
0.44.0                v0.44.0            0.33.93   1dd17270ec9bc9e764f314fa62c248406034edda

CTRL-PLANE-RELEASE   CTRL-PLANE-VERSION   CLUSTER
0.43.0                                 v.0.43.0                             k3d-k3s-default 

Additional context

Today, the workaround to find the version of the control plane running in the cluster is to use kubectl describe pod, e.g.

kubectl describe pod controller-6bc4fc97bc-5hq94 -n radius-system

Related issue: #8815

Would you like to support us?

  • Yes, I would like to support you

AB#15101

Activity

  1. added
    featureThis issue describes a feature request in Radius
    on Mar 24, 2025
  2. radius-triage commented on Mar 24, 2025

    @radius-triage

    👋 @willtsai Thanks for filing this feature request.

    A project maintainer will review this feature request and get back to you soon.

    We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

    For more information on our triage process please visit our triage overview

  3. radius-triage commented on Mar 26, 2025

    @radius-triage

    👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

    We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

    For more information on our triage process please visit our triage overview

  4. brooke-hamilton commented on Mar 26, 2025

    @brooke-hamilton
    Member

    @willtsai should we add something to the product roadmap related to supported/unsupported scenarios for backward and forward compatibility of the CLI vs. server versions?

  5. added a commit that references this issue on May 13, 2025
    9e5c2fd
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

    featureThis issue describes a feature request in RadiustriagedThis issue has been reviewed and triaged

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions