-
Notifications
You must be signed in to change notification settings - Fork 194
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
helm: add privileged option for running in ARO #364
Conversation
…ith privileged: true For OpenShift SCC requires privileged: true and also 2 settings below : for the CSI Driver : oc adm policy add-scc-to-user privileged system:serviceaccount:$target_namespace:secrets-store-csi-driver for the Azure KV Provider : oc adm policy add-scc-to-user privileged system:serviceaccount:$target_namespace:csi-secrets-store-provider-azure
the HELM Chart was correctly running with privileged: true |
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.
@ezYakaEagle442 As mentioned in the PR template:
<!--
**Is this a chart or deployment yaml update?**
If yes, please update the yamls in the [manifest_staging/](https://github.com/Azure/secrets-store-csi-driver-provider-azure/tree/master/manifest_staging/) folder, where we host the staging charts and deployment yamls. All the yaml changes will then be promoted into the released charts folder with the next release. Please also add the new configurable values to the configuration [table](https://github.com/Azure/secrets-store-csi-driver-provider-azure/tree/master/manifest_staging/charts/csi-secrets-store-provider-azure#configuration).
-->
Could you make these changes in the manifest_staging/charts
dir instead?
Also, this change would be required for the deployment manifests and helm charts in the manifest_staging
dir.
I've also opened an issue to track the documentation for this: #365 |
For OpenShift SCC requires
privileged: true
and also 2 settings below:Reason for Change:
Requirements
Issue Fixed:
Does this change contain code from or inspired by another project?
If "Yes," did you notify that project's maintainers and provide attribution?
Special Notes for Reviewers: