-
### TL;DR
Following customs on kubernetes resource distribution, it would be nice to have a chart that could be used to install the provider, similar to https://github.com/kubernetes-sigs/secrets-s…
-
I have deployed RKE2 using the example with CCM, adding my variables as stated in the docs, ssh key, floating ips and so on.
Deployed with 1 master and 3 workers. Everything gets running properly e…
-
### Proposal
Provide first-class support for using secrets through [Secrets Store CSI Driver](https://github.com/kubernetes-sigs/secrets-store-csi-driver).
### Use-Case
Allow end-users to use more …
-
### TL;DR
Add support for syncing to Kubernetes Secrets via `secretObjects`. See https://github.com/kubernetes-sigs/secrets-store-csi-driver#optional-sync-with-kubernetes-secrets
This would allow …
-
We would like to add additional volumes and volume mounts via the metrics-agent Helm chart so we can inject the API token via Secrets Store CSI Driver.
The below additional values would allow us to…
-
**What steps did you take and what happened:**
We have an Azure Key Vault with average requests lower than the KeyVault throttling limit.
and recently ran into outage when started using CSI Driver w…
-
### Motivation: Why do you think this is important?
To deploy to AWS flyte we need to pass a database password. The default method is to write the password with plain text or env variables in the c…
-
### Report
The problem is similar to the one described here: https://github.com/kedacore/keda/issues/555 when Deployment depends on Secret object that is not yet created. In our case the Secret is cr…
-
Currently, two option exist for referencing the License-File and DB-/Admin-credentials:
1. Via the secrets-store.csi.x-k8s.io/v1 API.
2. As a Kubernetes secret, directly created by the Helm-Chart.…
-
Hi, I use Vault by Hashicorp to manage my secrets and the CSI provider to sync them in my cluster.
To use this chart, I need some other values to be templated (serviceAccount, extraVolumes and extraV…