Repository navigation
rad cli chooses to use control plane of older version #8815
Description
Steps to reproduce
- Install a older radius version cli and install radius control plane with rad init.
- Download latest cli
nithya@MacBook-Pro mynewapp % rad version
RELEASE VERSION BICEP COMMIT
0.44.0 v0.44.0 0.33.93 1dd17270ec9bc9e764f314fa62c248406034edda
- Run rad init again:
nithya@MacBook-Pro myapp % rad init
Initializing Radius. This may take a minute or two...
✅ Use existing Radius 0.43.0 install on kind-kind
✅ Use existing environment default
✅ Scaffold application myapp
✅ Update local configuration
Initialization complete! Have a RAD time 😎
I used rad cli 0.44, but it chose to work with the 0.43 control plane which was already installed.
This can lead to unexpected outcomes, since the cli might have added features which are not supported by control plane of earlier version.
Workaround: uninstall radius and then do a rad init.
Expected Result: rad cli should use the existing control plane only when the version is matched.
Activity
[-]rad cli chooses to use old control plane if one is installed.[/-][+]rad cli chooses to use control plane of older version[/+]radius-triage commentedon Mar 12, 2025
👋 @nithyatsu Thanks for filing this bug report.
A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.
For more information on our triage process please visit our triage overview
ytimocin commentedon Mar 12, 2025
How does
rad install kubernetes --reinstallwork in this case @nithyatsu?brooke-hamilton commentedon Mar 13, 2025
Without a supported upgrade scenario, would it make sense to run
rad uninstallfirst?@willdavsmith running
rad install kuberneteson top of an existing installation could be an upgrade scenario.radius-triage commentedon Mar 24, 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
willtsai commentedon Mar 24, 2025
Having the CLI and control plane versions being independent of each other is intentional as a user may have the latest CLI installed but want their cluster to use an older version of Radius (perhaps for stability or change management policy reasons, etc.).
However, I agree that it's a confusing UX today given that the user only has visibility into the version of their CLI and not the version of the control plane running on the cluster they are pointed to. Thus, I've created a new feature request to enhance the UX for
rad version- #8953kachawla commentedon Mar 26, 2025
@willtsai for users who want to upgrade control plane as well, would we guide them to
rad upgradeinstead of providing a config onrad init?