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

Additional example for usage of CSI with Service Principal when deploying resources in different namespaces #241

Closed
akav opened this issue Sep 25, 2020 · 2 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Milestone

Comments

@akav
Copy link

akav commented Sep 25, 2020

Documentation provided for usage of Service Principal:
https://github.com/Azure/secrets-store-csi-driver-provider-azure/blob/master/docs/service-principal-mode.md

If one applies the secrets-store-creds and SecretProviderClass in default namespace only, when one deploys resources in namespace other than default containers will generate not found errors. It would be helpful to expand the documentation and mention that if one wishes to use the mounted volume that they would need to apply both secrets-store-creds and SecretProviderClass to each namespace where we wish our resources to have access to KeyVault.

Which access mode did you use to access the Azure Key Vault instance:
Service Principal

Environment:

  • Kubernetes version: 1.17.11
  • Cluster type: AKS
@akav akav added the enhancement New feature or request label Sep 25, 2020
@aramase aramase added the documentation Improvements or additions to documentation label Sep 29, 2020
@aramase aramase added this to the Stable milestone Nov 9, 2020
@pradorodriguez
Copy link

Also, if you try to sync the Secrets in other Namespaces it fails.

@aramase
Copy link
Member

aramase commented Apr 13, 2021

Closed with #468

@aramase aramase closed this as completed Apr 13, 2021
Secret Store CSI Azure Provider Roadmap automation moved this from To do to Done Apr 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Development

No branches or pull requests

3 participants