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
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
👋 @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
👍 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
@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?
Activity
radius-triage commentedon Mar 24, 2025
👋 @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
radius-triage commentedon Mar 26, 2025
👍 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
brooke-hamilton commentedon Mar 26, 2025
@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?
Updating rad version command to also show control plane version (#9167)