Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rad cli not aware of radius when installed with helm #8127

Open
1 task done
superbeeny opened this issue Dec 12, 2024 · 3 comments
Open
1 task done

rad cli not aware of radius when installed with helm #8127

superbeeny opened this issue Dec 12, 2024 · 3 comments
Labels
bug Something is broken or not working as expected triaged This issue has been reviewed and triaged

Comments

@superbeeny
Copy link
Contributor

superbeeny commented Dec 12, 2024

Steps to reproduce

  1. With a clean cluster and no corresponding entry in ~/.kube/config install radius via the helm chart as described here
  2. Enter rad group create dev returns an error
  3. Enter rad workspace create kubernetes dev and ensure the command executes successfully.
  4. Enter rad group create dev and rad env create dev -g dev, both should now execute successfully.
  5. Update the workspace with rad create workspace kubernetes dev -g dev -e dev --force

Observed behavior

No response

Desired behavior

The rad cli is aware of the radius deployment and when creating the workspace should env and group be created if they do not exist?

Workaround

Workaround in steps to reproduce

rad Version

RELEASE VERSION BICEP COMMIT
0.40.0 v0.40.0 0.31.92 91603b3

Operating system

macOS Sequoia m1

Additional context

No response

Would you like to support us?

  • Yes, I would like to support you

AB#13796

@superbeeny superbeeny added the bug Something is broken or not working as expected label Dec 12, 2024
@radius-triage-bot
Copy link

👋 @superbeeny 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

@sylvainsf sylvainsf added the triaged This issue has been reviewed and triaged label Dec 12, 2024
@radius-triage-bot
Copy link

👍 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

@rynowak
Copy link
Contributor

rynowak commented Dec 13, 2024

It was an intentional choice for rad workspace to not mutate state on the server.

Part of the motivation was that we had a lot of confusion about whether rad workspace was a client-side concept or a server-side concept (it's a purely client-side concept, like a KubeConfig).

I think there's some value digging into the scenario as you encountered it:

What should be the experience when you install Radius from Helm? What's created for you by default and what's not?

/cc @zachcasper - any thoughts about the scenario?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken or not working as expected triaged This issue has been reviewed and triaged
Projects
None yet
Development

No branches or pull requests

3 participants