-
Notifications
You must be signed in to change notification settings - Fork 99
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
Init ucp secret at server start #4674
Conversation
@@ -24,6 +24,11 @@ storageProvider: | |||
etcd: | |||
inmemory: true | |||
|
|||
secretProvider: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add kuberentes secret for helm chart.
https://github.com/project-radius/radius/blob/main/deploy/Chart/charts/ucp/ucp-config.yaml
And then ensure that ucp service account has secret resource permission.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching this. I have added the config I missed. For the permissions, I added secrets permissions to ucp.dev only, as those will be serving ucp secret
@@ -40,6 +40,7 @@ rules: | |||
- ucp.dev | |||
resources: | |||
- resources | |||
- secrets |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't right. Kubernetes secrets are part of the "core" group. We should already have permission to access secrets.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh thanks clarifying. I will change this back
…sions already exist
Description
This change initializes ucp secret client on startup
Issue reference
Fixes: #3595
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: