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

Ability to set static secrets under secretObjects #1342

Open
pdefreitas opened this issue Oct 18, 2023 · 0 comments
Open

Ability to set static secrets under secretObjects #1342

pdefreitas opened this issue Oct 18, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@pdefreitas
Copy link

Describe the solution you'd like
Some tools rely on synced Kubernetes secrets which may contain fields which do not make sense to be stored within Azure Key Vault, e.g. some Argo CD repository settings.

Anything else you would like to add:
I've seen multiple requests for such feature, even PRs but they never end up being released.
Related issues: kubernetes-sigs/secrets-store-csi-driver#938 , kubernetes-sigs/secrets-store-csi-driver#948 , kubernetes-sigs/secrets-store-csi-driver#1153
GCP PR: GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp#174

SCSI Community meeting notes of May 26, 2022:
Ability to set static secrets under secretObjects

  • This can be a feature request in the provider to set static values
  • Provider needs to return the file as part of the grpc response
  • Sync secret relies on the files in the mount, so it’ll work with any changes in driver

Environment:

  • Secrets Store CSI Driver version: (use the image tag): latest
  • Azure Key Vault provider version: (use the image tag): latest
  • Kubernetes version: (use kubectl version): 1.26.x
  • Cluster type: (e.g. AKS, aks-engine, etc): AKS
@pdefreitas pdefreitas added the enhancement New feature or request label Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant